You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by fe...@apache.org on 2005/07/29 13:12:19 UTC
svn commit: r226346 - /forrest/trunk/site-author/forrest.properties
Author: ferdinand
Date: Fri Jul 29 04:12:11 2005
New Revision: 226346
URL: http://svn.apache.org/viewcvs?rev=226346&view=rev
Log:
Added forrest.maxmemory setting so that site-author builds without error
Modified:
forrest/trunk/site-author/forrest.properties
Modified: forrest/trunk/site-author/forrest.properties
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/forrest.properties?rev=226346&r1=226345&r2=226346&view=diff
==============================================================================
--- forrest/trunk/site-author/forrest.properties (original)
+++ forrest/trunk/site-author/forrest.properties Fri Jul 29 04:12:11 2005
@@ -33,3 +33,6 @@
# comma separated list (no spaces)
# Run "forrest available-plugins" for a list of plug-ins currently available
project.required.plugins=org.apache.forrest.plugin.input.dtdx,org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.output.POD,org.apache.forrest.plugin.output.pdf,org.apache.forrest.plugin.output.Text,org.apache.forrest.plugin.input.wiki,org.apache.forrest.plugin.input.OpenOffice.org
+
+# Max memory to allocate to Java
+forrest.maxmemory=128m
\ No newline at end of file
Re: attracting attention to issues (Was: svn commit: r226346)
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
>
> We should start using Jira to send a summary
> of key issues to the dev list to remind us.
I have recently been experimenting with the "subscriptions" in Jira. I
can set it up so that we get a regular mail listing all issues in a
particular search.
I can set up a subscription for the dev list that sends a list of all
open issues against the last release and all critical or blocker issues?
I propose sending this once a week, say Tuesday.
I'll do this sometime next week unless there is a -1 (lazy consensus in
operation).
Ross
attracting attention to issues (Was: svn commit: r226346)
Posted by David Crossley <cr...@apache.org>.
ferdinand@apache.org wrote:
>Author: ferdinand
>Date: Fri Jul 29 04:12:11 2005
>New Revision: 226346
>
>URL: http://svn.apache.org/viewcvs?rev=226346&view=rev
>Log:
>Added forrest.maxmemory setting so that site-author builds without error
>
...
>+# Max memory to allocate to Java
>+forrest.maxmemory=128m
The trouble with adding a workaround to SVN is that
people are then less inclined to investigate the problem.
Out of sight, out of mind.
My technique was to just send mail to the mailing list
to say that i had to increase it. I should have also
explained it better at issue FOR-572 and raised the
priority.
We should start using Jira to send a summary
of key issues to the dev list to remind us.
David
possible memory problems FOR-572 (Was: svn commit: r226346)
Posted by David Crossley <cr...@apache.org>.
Johannes Schaefer wrote:
> is there a wholesite.html/pdf in it?
> this uses a lot of memory (we hit this problem heavily).
There is no wholesite PDF, thank heaven.
> on the other hand image processing/generation may
> be a penalty: any (big) images added recently?
No.
Thanks for trying.
David
Re: svn commit: r226346 - /forrest/trunk/site-author/forrest.properties
Posted by Johannes Schaefer <jo...@uidesign.de>.
is there a wholesite.html/pdf in it?
this uses a lot of memory (we hit this problem heavily).
on the other hand image processing/generation may
be a penalty: any (big) images added recently?
Johannes
Ross Gardler schrieb:
> Ferdinand Soethe wrote:
>
>>
>> Ross Gardler wrote:
>>
>>
>>> Hmmm... we had better create an issue for this, it smells of a memory
>>> leak.
>>
>>
>>
>> Don't get me wrong I just took the first size that worked. Doesn't
>> mean it has to be this much.
>
>
> Yeah, I understand that, but I can't think of any reason why we need to
> increase the maxmemory just because the site has got bigger, we are
> still only processing one file at a time.
>
> You are the third person to hit this problem now, so we can be pretty
> sure it is not down to an individuals installation.
>
> Does anyone have any ideas why we suddenly need more memory?
>
> Ross
>
>
--
User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg
Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99
Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * D-81825 München
www.uidesign.de
Buch "User Interface Tuning" von Joachim Machate & Michael Burmester
www.user-interface-tuning.de
Re: svn commit: r226346 - /forrest/trunk/site-author/forrest.properties
Posted by Ross Gardler <rg...@apache.org>.
Ferdinand Soethe wrote:
>
> Ross Gardler wrote:
>
>
>>Hmmm... we had better create an issue for this, it smells of a memory leak.
>
>
> Don't get me wrong I just took the first size that worked. Doesn't
> mean it has to be this much.
Yeah, I understand that, but I can't think of any reason why we need to
increase the maxmemory just because the site has got bigger, we are
still only processing one file at a time.
You are the third person to hit this problem now, so we can be pretty
sure it is not down to an individuals installation.
Does anyone have any ideas why we suddenly need more memory?
Ross
Re: svn commit: r226346 - /forrest/trunk/site-author/forrest.properties
Posted by Ferdinand Soethe <fe...@apache.org>.
Ross Gardler wrote:
> Hmmm... we had better create an issue for this, it smells of a memory leak.
Don't get me wrong I just took the first size that worked. Doesn't
mean it has to be this much.
--
Ferdinand Soethe
Re: svn commit: r226346 - /forrest/trunk/site-author/forrest.properties
Posted by Ross Gardler <rg...@apache.org>.
ferdinand@apache.org wrote:
> Author: ferdinand
> Date: Fri Jul 29 04:12:11 2005
> New Revision: 226346
>
> URL: http://svn.apache.org/viewcvs?rev=226346&view=rev
> Log:
> Added forrest.maxmemory setting so that site-author builds without error
>
...
> +# Max memory to allocate to Java
> +forrest.maxmemory=128m
Hmmm... we had better create an issue for this, it smells of a memory leak.
Ross