I have been happy with Devonsphere Express, except for one significant annoyance.
When it is updating the index, it and the devonbot process peg the processor (on a 3GHz core 2 duo). The whole computer is almost unresponsive for the 5-10 seconds (or occasionally longer?) required.
Is it possible to have the index go at half throttle (so to speak) so that other apps are not so affected.
After all, isn’t indexing supposed to be a background process?
Thank you for the suggestion! Could you please send the file ~/Library/Application Support/DEVONsphere Express/Logs/devonbot/default.log to cgrunenberg - at - devon-technologies.com?
Just to say I’m trialling DEVONsphere and have the exact same problem – devonbot hogs all the processor cycles (and a HUGE chunk of real memory) rendering the MBP almost unusable until it stops. This is not friendly software!
To be fair, I’ve not noticed such a big impact on performance today. It may have been during the initial indexing that it was having a bigger impact. The effect is still clearly noticeable, though, e.g. menus, file dialogue boxes etc. slow to appear, and devonbot/DSE still grabbing all available cycles and memory
I just want to add that I’ve been noticing the same problems.
With Devonsphere Express running I notice a slow down of the system. E.g. apps are starting up much slower etc.
Any news on finding out how to solve the problem? Except for shutting down Devonsphere?!
My system is a MacBook Pro Early 2011, 2.3 GHz Intel Core i5, 8 GB RAM
I will send out the log file later.
I see three processes running in Activity Monitor:
devonbot (not responding) 70% cpu
devonbotd32 12% cpu
devonbotd64 12% cpu
What’s with all the devonbots? Why are my fans running full speed?
Once the indexing FINALLY finished (10 full minutes) my machine is back to normal. I viewed the preferences dialog in DevonSphere Express and saw it was indexing my email. Fair enough, but I WISH IT WOULD GET A MOVE ON!
can’t upload my log file because I get an error saying The extension is not allowed. funny. I removed the extension and get the same error.