Guru
Joined: 09/01/2022
Location: United KingdomPosts: 798
| Posted: 03:28pm 14 Apr 2025 |
One last data point, incase it triggers a brain wave.
Standard Bubble, with file open, & heap and without. & heap
Exactly as original, 225mS 165888 and 276mS 166400
Add 'Dim Integer e(1)' 252mS 165632 and 276mS 166144
No change by increasing dim size.
Make 'Dim Integer e(31)' 252mS 165632 and 276mS 166144
Make 'Dim Integer e(32)' 278mS 165376 and 277mS 165888
Exactly as original, 225mS 165888 and 276mS 166400
Add 'Dim Integer e(1)' 252mS 165632 and 276mS 166144
No change by increasing dim size.
Make 'Dim Integer e(31)' 252mS 165632 and 276mS 166144
Make 'Dim Integer e(32)' 278mS 165376 and 277mS 165888
So the speed drops in steps as the heap gets larger by increasing the dim size when a file is open, but the speed does not change with no file open.
Note that the speed when the heap jumps to 165376, with an open file, gives the exact same speed as with no file open, ie no speed up. (when e is an array of 33).
This also happens to be the point when the heap is 165888, without an open file, which is exactly the same size as the original, with no dim defined, but with a file open and the fastest speed??
But whatever I try I can't get even close to the 225mS by simply playing around with variable definitions or Frame buffers.
Is there anything I can define that shifts or alligns the memory layout in different ways, maybe defining a C function or something, so I can experiment a bit more?
Edited 2025-04-15 01:30 by Bleep