|Message: Re: Heavily throttled job?||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
I don't know if this will turn out to be it for you, but perhaps...
I had a very similar performance issue when I was running jobs are many different CPUs at the same time. It turned out that I had my code set to write out the current random seed after each event. Since all of my 100 jobs were all trying to write the seeds out to files on the same AFS volume, I got only about 5% of my CPU actually used. Solution was just to switch so that I only wrote the seed out at end of job, not end of event.
Are you writing a lot of random seeds out?
Are you running multiple jobs all using the same disk volume in some way?
|Inline Depth:||Outline Depth:||Add message:|