Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How often is SYS(2015) changed?
Message
From
07/09/2011 10:18:54
Dragan Nedeljkovich
Now officially retired
Zrenjanin, Serbia
 
 
To
07/09/2011 09:25:59
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01521892
Message ID:
01522897
Views:
53
>>>>But I prefer to use hexadecimal value that will always result 4 bytes length.
>>>>
>>>>
>>>>m.lcNewID = SYS(2015) + RIGHT(TRANSFROM(Application.ThreadId, "@0"), 4)
>>>>
>>>>
>>>>What do you think, sir?
>>>>
>>>>
>>>>Regards,
>>>>Onytoo
>>>
>>>You are only creating the name of a variable, so the difference will be zero.
>>
>>Actually, one: one byte per key value.
>
>My point was that the length of the variable itself, should have close to no influence on the result. And by result I mean the processing time.

This being a key, and the likelihood that the extra byte will cause the blocks to fill a tad faster... if a single instance of the app is likely to issue multiple such keys, I'd rather put the thread it (represented by either 4 or 5 bytes) first, and sys(2015) second. Then the first nine bytes, at least, may be the same for all the keys issued by the same instance, which should help Rushmore engine to keep them small, hence use less memory etc. I expect a whooping 1% of increased performance in that case.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform