See if the latest version still has this issue.
Some actions use multiple cores. The primary users are
Thumbnails are computed in the background, and if a lot of graphs change at the same time this can take up CPU resources. This is generally a good thing since the machine will stay more responsive. To avoid this, you can use the grouping mechanism for the graph (in the beta), put the graphs in a group and close the group. The thumbnails will not be recreated.
Exporting a movie, bitmap rendering and movie creation is done in a separate thread.
LOESS smoothing, since it involves a lot of computation.
Import Special, when you import data.
I tweaked one threaded action in the latest beta, related to undoing imports/paste. Don’t know if that affected this.
I’m always interested in cases where DataGraph feels slow. The steps to fix that is to look into the algorithm used, and then start threading the operation. That will increase the CPU power to over 100%, but with machines getting more and more cores this is how that extra CPU power is used.
Note however if the memory footprint increases unreasonably. That really slows down the machine as it needs to swap memory to disk.
petercreate.
petercreate
david