Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Sudden slowdown
69 views
Skip to first unread message
Ian Boys
Apr 12, 2013, 10:04:13 AM4/12/13
to
Hi,
I'm (still) using Clipper 5.2e with a Six3 CDX indexed database(and I
know that I should go to Harbour, but that does not solve this issue).
Suddenly my programme seems to be really slowly accessing its main
database over a network.
Executing the bit of code below was virtually instantaneous (you never
really saw the first message) but now seems to generate a 1 to 5 second
delay.
@ 14,0 say 'Moving to record'
pat->(dbgoto(xrecno))
@ 14,0 say 'Updating queue'
I did have a seek in there originally but replaced it with a goto to try
to speed it up.
The only overall changes that I am aware of doing was taking out a bunch
of redundant site specific code, none of which would affect the above 3
lines of code but has reduced the exe size by about 4kb.
Any ideas would be appreciated.
Regards
Ian Boys
DTE
I'm (still) using Clipper 5.2e with a Six3 CDX indexed database(and I
know that I should go to Harbour, but that does not solve this issue).
Suddenly my programme seems to be really slowly accessing its main
database over a network.
Executing the bit of code below was virtually instantaneous (you never
really saw the first message) but now seems to generate a 1 to 5 second
delay.
@ 14,0 say 'Moving to record'
pat->(dbgoto(xrecno))
@ 14,0 say 'Updating queue'
I did have a seek in there originally but replaced it with a goto to try
to speed it up.
The only overall changes that I am aware of doing was taking out a bunch
of redundant site specific code, none of which would affect the above 3
lines of code but has reduced the exe size by about 4kb.
Any ideas would be appreciated.
Regards
Ian Boys
DTE
dlzc
Apr 12, 2013, 11:18:06 AM4/12/13
to
Dear Ian Boys:
On Friday, April 12, 2013 7:04:13 AM UTC-7, Ian Boys wrote:
...
> with a Six3 CDX indexed database(and I know
> that I should go to Harbour, but that does
> not solve this issue).
So you have identical code, running 32-bit native Windoze console, and it has exactly the same delay? Please confirm you tried this, when you say it does not solve it.
> Suddenly my programme seems to be really
> slowly accessing its main database over a
> network.
If it is slow on the server end (depending on your answer above), then what changed on the server? Look for Micro$hit updates (they just pushed a bunch), and antivirus program changes.
...
> The only overall changes that I am aware of
> doing was taking out a bunch of redundant site
> specific code, none of which would affect the
> above 3 lines of code but has reduced the exe
> size by about 4kb.
Add a "SET FILTER TO" before running it.
> Any ideas would be appreciated.
You have made some terse assertions here, and challenging them is about all I can offer here. If the OS did not change (and you should assume it will, Micro$hit needs us to buy Windoze 8), and you acknowledge you changed your code, then you did to this yourself.
You will get marked performance improvements by moving *now* to (x)Harbour. Also, you should be much less dependent on OS changes, and your clients can get 64-bit OS machines, and not worry about how to make 16-bit programs run on those machines. Add in the extra capabilities of calling and interoperating with Windows programs, and your customer can only be happier.
David A. Smith
On Friday, April 12, 2013 7:04:13 AM UTC-7, Ian Boys wrote:
...
> I'm (still) using Clipper 5.2e
... OK, so this means you are running 16-bit NTVDM and COMMAND.COM.
> with a Six3 CDX indexed database(and I know
> that I should go to Harbour, but that does
> not solve this issue).
> Suddenly my programme seems to be really
> slowly accessing its main database over a
> network.
...
> I did have a seek in there originally but
> replaced it with a goto to try to speed it up.
Do not do black magic programming. If it is not a Windoze delay, then it seems to me you have changed your code and have an errant filter that is still in effect.
> replaced it with a goto to try to speed it up.
> The only overall changes that I am aware of
> doing was taking out a bunch of redundant site
> specific code, none of which would affect the
> above 3 lines of code but has reduced the exe
> size by about 4kb.
> Any ideas would be appreciated.
You will get marked performance improvements by moving *now* to (x)Harbour. Also, you should be much less dependent on OS changes, and your clients can get 64-bit OS machines, and not worry about how to make 16-bit programs run on those machines. Add in the extra capabilities of calling and interoperating with Windows programs, and your customer can only be happier.
David A. Smith
Ian Boys
Apr 13, 2013, 5:15:08 AM4/13/13
to dlzc
David,
Thanks for the reply. I don't use MS servers so I know that had not
changed. And, yes, I do need to move over to Harbour but that will take
time and this was an active issue.
I took a look at http://www.donnay-software.com/memory.htm Clipper
Memory Management and placed a Memory(-1) and the problem went. Strange
that this issue raised its head after 20 years.
Regard
Ian Boys
DTE
Thanks for the reply. I don't use MS servers so I know that had not
changed. And, yes, I do need to move over to Harbour but that will take
time and this was an active issue.
I took a look at http://www.donnay-software.com/memory.htm Clipper
Memory Management and placed a Memory(-1) and the problem went. Strange
that this issue raised its head after 20 years.
Regard
Ian Boys
DTE
0 new messages