For manifoldcf with postgres, CPU usage can be considerable, and disk usage as well. Solr has a similar profile. But I would separate the two to avoid disk contention, unless you have ssds.
Karl Sent from my Windows Phone ------------------------------ From: Ronny Heylen Sent: 11/9/2013 3:52 AM To: Karl Wright; [email protected] Subject: Re: Tomcat\temp is not empty after Manifoldcf job The windows machines we can define for Solr/Manifoldcf are VM running on a physical server with 12 cores, 8 available for Manifoldcf/Solr. Is it better to define 1 windows machine with 8 cores running Solr and Manifoldcf, or 1 machine 4 cores for Solr and another one 4 cores for Manifoldcf? Thanks, On Sat, Nov 9, 2013 at 7:27 AM, Karl Wright <[email protected]> wrote: > Hi Ronny, > What deployment model are you using for manifoldcf? Combined or > multiprocess? > > Karl > > Sent from my Windows Phone > ------------------------------ > From: Ronny Heylen > Sent: 11/8/2013 2:47 PM > To: [email protected] > Subject: Tomcat\temp is not empty after Manifoldcf job > > A big manigofldcf job has run, indexing 245000 documents from windows > disk to SOLR. > When the job run, you can see lot of files appearing and then disappearing > from tomcat\temp, all named upload_e6a423e_1423883e249__8000_xxxxxxxx.tmp > xxxxxxxx being a counter (00000001, 00000002, ...) > When the job is finished, +/- 20 such upload... files are left in the temp > folder. > Is this normal? >
