Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Can i speed this up ??
Message
From
07/07/2006 09:44:17
Suhas Hegde
Dental Surgeon
Sirsi, India
 
 
To
07/07/2006 04:20:00
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
01134026
Message ID:
01134416
Views:
28
>>Yes , this is for the stock market application i am using for my personal ends. It is a new parameter called Noise of the data ... the most number of price ranges in the period... I even thought abt adding the whole years data and saving the cursor but it kills the basic logic of the noise for the period ....
>>
>>also in case i do use it by having many cursors like each for the 80 values... there would be lot of unnecessary over head suppose 400 records ??? then the number of cursors would be 400-80 = 320....
>
>I have some trouble visualizing your layout - you need one "foo" table for each stock for each window of measurements (the 80 days or hours or whatever) to replace the part of code aleady shown. Since the 80 is hardcoded I guessed it to be a constant number. If you research more than a couple of hundred stocks, create a table for "noise" with a key added for the stocks - instead or creating a empty cursor work on the records for that stock only. Even reading the records for one stock into a temp cursor, correcting there and saving back into the table/cursor for all stocks should be faster than your current approach. But having data for all stocks in one precalculated table:
>
>removes the time to create tmp cursor
>removes the time to index tmp cursor
>removes the time of roughly 78/80 of the replace operations you currently have
>
>when replacing:
> - adds some mimimal time if using rushmore because of larger cdx
> - should take minimal time more for seek, same time for replace (using Craig's faster method)
> - you could check out set key
>
>HTH
>
>thomas

Hi,
80 is actually not hard coded (in the example it is ), I used it for better clearity...

The 'NOISE' is dynamically calculated .. as u can see.

SO

if i have create noise for all the scripts (abt 1013 and continouslly added) for a period of 3 years (300 days per year * 3) and the noise data as the scripts ranges some times from .5 to 3000 for the same script (yo, thats a lot of appriciation and unlucly i was not a part of it) i just cannot imagine the storage space recquired ...

also my application consistes of 3 main files...

1) exe
2) one dbf
3) one cdx

and the data that i download goes into it.

If thats the fastest i can get the i will have to bear with it ( what else can i do )

thanx for your views

suhashegde
Previous
Reply
Map
View

Click here to load this message in the networking platform