-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noah,
On 3/16/2011 10:47 PM, Noah Cutler wrote:
> I'll need to sort out DBCP, java singletons are nothing like php where a
> singleton exists for lifetime of the request, vs. lifetime of the
> application.
The servlet spec includes a "request" object
Chris,
will likely go with mod_jk, but I did notice that Jetty folks strongly
recommend mod_proxy (may be that their container works better with
mod_proxy)
I am not using a framework per se, one that I have written, so
definitely not something like Grails with Spring + Hibernate for
example. Gro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noah,
On 3/16/2011 7:48 PM, Noah Cutler wrote:
> the Tomcat Groovy app will do nothing but serve up dynamic content
> (httpd will handle ssl as well), so whichever method (ajp or mod_proxy)
> peforms the best/is-most-reliable, I'll go with.
I have a
Chris, great feedback.
the Tomcat Groovy app will do nothing but serve up dynamic content
(httpd will handle ssl as well), so whichever method (ajp or mod_proxy)
peforms the best/is-most-reliable, I'll go with.
Love that 128mb JVM, I am very much interested in lean & mean. Coming
from LAMP stack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noah,
On 3/15/2011 7:02 PM, Noah Cutler wrote:
> However, some of the LAMP stack apps will have legacy/archived
> functionality that I have zero interest/time in porting over to
> JVM/Groovy framework. So, the plan is to mod_rewrite archived requests
Thomas,
yes, I have seen a few sample mod_jk configs, does not look difficult to
implement.
Load balanced, per instance and/or virtual host setup with new DBCP,
what more could one ask for ;--)
I am really looking forward to generating dynamic content with Groovy on
Tomcat, quite lightweight com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Noah,
On 03/15/2011 07:05 PM, Noah Cutler wrote:
> Obviously per instance is a memory hungry solution, albeit highly
> convenient. Placing all sites in a single instance is a possibility as
> well (and the most resource "friendly"), but I would nee
Chris, thanks for the excellent feedback; thus far this list exceeds
Stackoverflow by orders of magnitude ;--)
Re: ease of implementation, yes, a single instance with multiple virtual
hosts is the way to go (similar setup to apache virtual hosts).
However, some of the LAMP stack apps will have le
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noah,
On 3/15/2011 2:05 PM, Noah Cutler wrote:
> Obviously per instance is a memory hungry solution, albeit highly
> convenient. Placing all sites in a single instance is a possibility as
> well (and the most resource "friendly"), but I would need to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noah,
On 3/15/2011 3:27 AM, Noah Cutler wrote:
> So, given that a running 32-bit JVM on Linux will require at least 1GB
> RAM, total memory usage will not be JVM footprint * num instances, but
> rather, JVM footprint + num instances?
Not necessarily.
Thomas, perfect, hours of searching Stackoverflow et al resolved in a
single mailing list thread ;--)
I will play around with various configs (per instance and multi-host per
instance) in my local devel to get an idea of no-load resource usage;
then, as you say, give some % more to avoid OOMEs in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Noah,
On 14.03.11 um 21:27, Noah Cutler wrote:
> So, given that a running 32-bit JVM on Linux will require at least 1GB
> RAM, total memory usage will not be JVM footprint * num instances, but
> rather, JVM footprint + num instances?
Actually, the
Thomas, excellent, informative.
So, given that a running 32-bit JVM on Linux will require at least 1GB
RAM, total memory usage will not be JVM footprint * num instances, but
rather, JVM footprint + num instances?
The use case is transferring 20 client sites from LAMP stack to JVM +
Tomcat 7 + MyS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Noah,
On 03/15/2011 06:25 AM, Noah Cutler wrote:
> can find nothing on the net re: this apparently basic question.
>
> Given a simple hello world "app", what is the @memory footprint per
> instance in Tomcat 7?
>
> Just trying to assess options v
Hi,
can find nothing on the net re: this apparently basic question.
Given a simple hello world "app", what is the @memory footprint per
instance in Tomcat 7?
Just trying to assess options visa vi single instance + multiple virtual
hosts vs. multiple instance single host (preferred option as each
15 matches
Mail list logo
