Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

collection-service memory usage

Created: 02 Jul 2012 | 5 comments
benjus10's picture

Hi All,

I've been trolling the internet looking for a hint here but so far no luck, so hopefully one you has come across this.

I have a new installation of EV 10.0.1 all running fine but the collection-service just keeps consuming memory, restarting the Indexing service resets it back to near zero but then it continues to climb, it is currently at 4.5Gb.

The server has 8Gb RAM and 8GB pagefile on a dedicated disk.

Is this by design or something I need to be concerned with? Is there a way to cap the usage?

Many thanks

Comments 5 CommentsJump to latest comment

Wayne Humphrey's picture

Hi benjus10,

Collection Service? Or do you mean the PST Collection Task? If so yes I have seen it utilise quite a bit of memory before.  You could always run a trace on the PST Collector Task to verify it’s all ok

If you have not use Dtrace before please see:

http://www.symantec.com/business/support/index?page=content&id=TECH38122

https://www-secure.symantec.com/connect/articles/enterprise-vault-dtrace

benjus10's picture

Hi Wayne,

Not the PST collector, it's collection-service.exe which is part of the indexing services which in turn spawns other indexing services.  

Wayne Humphrey's picture

 collection-service.exe never heard of that tbh...

Rob.Wilcox's picture

I've also seen it use a fair amount of RAM, but to be honest these are just in my test labs - I don't have access to a production EV 10 (or 10.0.1) server.  So.. I would a/ monitor it b/ open a support case.

It could be that it operates just like SQL and Exchange, in that it will consume all available RAM, and then release it other processes when the OS instructs it to do so.