CPU usage during indexing

Rick Williams

This is just an observation, not a complaint but I've noticed that L5 seems more agressive in its use of CPU resources than L4, which wasn't shy.  This morning an 11 resource update downloaded and during the initial part of indexing L5 took 86% of the CPU on an i7 machine w/9GB ram running at 2.67 Ghz.  When the fans and cooling systems kicked in, it sounded like a jet taking off...g  Then for a bit it ran around 42% before settling into a cycle of between 1-16%.  The only other software I have that comes close to these numbers is a professional video editing suite and it has never hit anything above 55%.

Has anyone else noticed this?

Patrick S.

This is just an observation, not a complaint but I've noticed that L5 seems more agressive in its use of CPU resources than L4, which wasn't shy.  This morning an 11 resource update downloaded and during the initial part of indexing L5 took 86% of the CPU on an i7 machine w/9GB ram running at 2.67 Ghz.  When the fans and cooling systems kicked in, it sounded like a jet taking off...g  Then for a bit it ran around 42% before settling into a cycle of between 1-16%.  The only other software I have that comes close to these numbers is a professional video editing suite and it has never hit anything above 55%.

Has anyone else noticed this?

This is normal for indexing, the indexing code will use as many cores as possible to get the job done as quickly as possible. It is only for one time task of indexing, not for normal use.