Performance
So far I'm loving what I've seen from a features perspective (still discovering though).
However, the application is running incredibly slowly. Each click of the mouse requires a five (or more) second wait before something happens. When you are discovering features, this makes it really time consuming.
I'm running this on a 1.6GHz Atom (which doesn't seem to be stressed now that indexing is complete) with 2Gb RAM and a nice fast Intel SSD drive (which along with the memory, doesn't seen stressed either).
I know there are "optimizations" coming in the future, but is this going to be enough? Am I right in understanding that this is running in WPF? If so, perhaps the issues are related to graphics (shared memory graphics in particular perhaps).
Find more posts tagged with
Comments
Not at all responsive with my setup, to the point that I'm increasingly reluctant to attempt real work with it.I remember that the log was something 3.0 that we would only turn on when Logos needed to check a bug because it slowed the program down. When Logos 4 gets released will things speed up simply because the log isn't permanently on?
I've been monitoring my system resources (CPU, Memory, HD and Network activity) and found v4 calls home (to logos.com) more than ET ever wanted to. Just about every time I do a command/function or open a resource the HD and network activity goes up more than expected - sometimes the CPU and Network activity goes way up. I think that's why it seems slow - it's doing a bunch of background logging for the beta testing. I hope it goes away when we get to the latter beta versions and especially the release version. It also seems to "Sync" a lot (swirly thingy in top-right corner of screen spins) which means it's busy and slows things down.
The performance is worse as you add more open resources. This seems logical, but suggests that it is not graphics, but something else.
Having fewer resources open makes the product usabe (performance wise).