I'm curious if my performance is line with others and if I should do something to improve it which I have not understood to do.
When making longer track, more than 30km, I'm finding that BTB is updating each of four panels one by one every time when there is window on top of BTB, screensaver or if I make any change, this can take around 30 seconds which time I must wait.
Now I tested bit of extremes, I did import 1 061 615 meters of GPS data into BTB, wait time is around 7 minutes after each click on those buttons at top row, for example if I would like to change panel length to larger number so that export would work it takes 7 minutes to get there.
I have read people doing 500km or even longer tracks for really fast vehicles, as BTB is not using more than one core, I'm interested to know which kind of hardware is used to get better performance?
My current CPU is Intel core 2 duo E6750 and I have 3GB of ram, system is not supporting more as I'm using WinXP and not going to move into Vista or 7, have seen enough of those resource hogs at work.
I know of setting that causes updates only after I move nodes, but delay is then after moving node, so I have to wait 30 seconds for around 30km track, of course amount of nodes affects this too, but with GPS data there is node for each 15-30 meters (it varies by speed and some random things), so that makes as on average ~1333 nodes for 30km track.
Setting node type from spline to kardinal has sometimes improved performance from my experience.
Or maybe there is something else that should be done to reduce waiting times or is stronger CPU only medicine?
edit: Splitting the track, I have tried this, but can't really see the light in it, there seem not to be difference in performance what I have observed and even hiding nodes seem not to affect actual waiting time of window re-drawing.
When making longer track, more than 30km, I'm finding that BTB is updating each of four panels one by one every time when there is window on top of BTB, screensaver or if I make any change, this can take around 30 seconds which time I must wait.
Now I tested bit of extremes, I did import 1 061 615 meters of GPS data into BTB, wait time is around 7 minutes after each click on those buttons at top row, for example if I would like to change panel length to larger number so that export would work it takes 7 minutes to get there.
I have read people doing 500km or even longer tracks for really fast vehicles, as BTB is not using more than one core, I'm interested to know which kind of hardware is used to get better performance?
My current CPU is Intel core 2 duo E6750 and I have 3GB of ram, system is not supporting more as I'm using WinXP and not going to move into Vista or 7, have seen enough of those resource hogs at work.
I know of setting that causes updates only after I move nodes, but delay is then after moving node, so I have to wait 30 seconds for around 30km track, of course amount of nodes affects this too, but with GPS data there is node for each 15-30 meters (it varies by speed and some random things), so that makes as on average ~1333 nodes for 30km track.
Setting node type from spline to kardinal has sometimes improved performance from my experience.
Or maybe there is something else that should be done to reduce waiting times or is stronger CPU only medicine?
edit: Splitting the track, I have tried this, but can't really see the light in it, there seem not to be difference in performance what I have observed and even hiding nodes seem not to affect actual waiting time of window re-drawing.