Specific CPU issues with syncing and metadata updates

I've found that Logos slows way down and becomes CPU bound with the two things:

1. Syncing my resource priority list with the server. (whenever I update my preferred resounces)

2. Downloading metadata updates from the server. (often on startup)

During both of the my CPU usage is >80% and Logos is less than responsive. Plus it takes like 5 to 10 minutes to do either of these, so it's a real problem when it happens.

Also, if the resource priority is being sync'd, and I shut down Logos, then the Logos window disappears, but it's still running in my task list and still using CPU.

Find more posts tagged with

Comments

Todd Phillips

Also, if the resource priority is being sync'd, and I shut down Logos, then the Logos window disappears, but it's still running in my task list and still using CPU.

Okay I think this is a BUG.

I shutdown Logos 4 because it was taking up all the CPU while doing a sync (uploading the modified preferred list). Indexing was already paused to try to help it. The main Logos window disappears but the process never ends. (Though it actually does stop using the CPU)

Then trying to start up Logos again causes it to hang (because the previous instance is still around, I guess). Note the three Logos4.exe processes in the task manager.

When I kill the first one, the new instance then opens normally. Of course it restarts the sync, with the same CPU problems that caused my to shut it down:

View:http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/1234.Logos4.log

(this log is from when multiple processes were running)

Bradley Grainger (Logos)

1. Syncing my resource priority list with the server. (whenever I update my preferred resounces)

2. Downloading metadata updates from the server. (often on startup)

During both of the my CPU usage is >80% and Logos is less than responsive. Plus it takes like 5 to 10 minutes to do either of these, so it's a real problem when it happens.

For (1), we will be posting a fix for sync (that may be contributing to this problem) in SR-3 and SR-4. Edit: I misread your post, and also misunderstood the nature of the change that was being made to sync; we haven't made any changes to resource priority sync that would improve performance.

What are your system specs? And are you running under VMware/Fusion (which is not recommended, and dramatically hurts performance)?

Damian McGrath

https://community.logos.com/discussion/comment/27961#Comment_27961

1. Syncing my resource priority list with the server. (whenever I update my preferred resounces)

...

For (1), we will be posting a fix for sync (that may be contributing to this problem) in SR-3 and SR-4.

Please, this cannot come soon enough. Prioritisation has become a nightmare

Todd Phillips

https://community.logos.com/discussion/comment/27961#Comment_27961

What are your system specs? And are you running under VMware/Fusion (which is not recommended, and dramatically hurts performance)?

WinXP ThinkPad T42p with 2Ghz Pentium M, 2GB RAM (sorry, I removed it from my sig yesterday :-)

actually #2 is not as bad as number one, but it's still a problem and steals performance from the main app.

Todd Phillips

https://community.logos.com/discussion/comment/28171#Comment_28171

Logos4 also becomes CPU bound and non-responsive when it's syncing notes I've written, too. This is something I've discovered since I started using notes--also very irritating, since It tends to do it while I'm trying to edit the notes. It's hard to type when when the characters appear in spurts.

So...to sum up...syncing of prioritized resouces, syncing of notes, and start-up metadata-update checks all grab my CPU in a way that I have to wait until it's done if I don't want to be frustrated.

It's only Logos that response issues, BTW. Other apps respond fine during this time. An application threading issue?