[Seaside] Re: ZINC - Kom dilemma Fwd: WADebugErrorHandler problem
kuszinger at giscom.hu
Tue Jan 19 07:40:29 UTC 2016
thanks for the ideas and information. I'll also try this way also to ensure
every factor to be optimal.
Summarizing all the comments by far it seems that the bulletproof service
infrastructure is streaming upload to disk or possibly outside the
Smalltalk VM (nginx way) and keep other application data inside. Memory
limits are still interesting for safe handling of a larger parallel load.
Paul DeBruicker <pdebruic at gmail.com> ezt írta (időpont: 2016. jan. 19., K,
> Phil (list) wrote
> > On Tue, 2016-01-19 at 02:14 +0100, Stephan Eggermont wrote:
> >> > Assuming you're running the Cog VM you're likely hitting its memory
> >> > limits. I don't recall the exact number, but once you get to the
> >> > 400-
> >> > 500 Meg range you're hitting the absolute limit of how much RAM Cog
> >> > can
> >> > deal with.
> >> That is just default limits. On a mac I've worked with about 2GB.
> >> There
> >> used to be some limitation on windows, I think there was an issue in
> >> 2011 on windows where there was a limit closer to 512 GB, but AFAIk
> >> that
> >> was fixed.
> > Is that something that can be changed without a custom build? If so,
> > I'd love to learn how. I was under the impression that this was a hard
> > limit in Cog (that varies a bit by platform, but still well below 1G)
> On the mac you can change the limit in
> by adjusting the value for the SqueakMaxHeapSize setting and restarting the
> View this message in context:
> Sent from the Seaside General mailing list archive at Nabble.com.
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside