I think that the mod_perl mailing list would also be interested in this -
there are very few people on that list with practical examples of
multi-thread. As far as I'm aware pre-fork is still pretty much the only
model recommended.
Alejandro Imass wrote:
Ok. What would you have done? - not
On Thu, Jul 2, 2009 at 4:08 AM, Carl
Johnstonecatal...@fadetoblack.me.uk wrote:
I think that the mod_perl mailing list would also be interested in this -
there are very few people on that list with practical examples of
multi-thread. As far as I'm aware pre-fork is still pretty much the only
Hi! Sorry for the lethargy, I've buried in a project and just recently
saw the light of day :-)
Yes, you are correct [Tomas], BUT it all depends on the type of
application. Web concurrency is often misinterpreted. The application
I was referring to needs the ability to have many, many concurrent
On 30 Jun 2009, at 11:58, Alejandro Imass wrote:
Hi! Sorry for the lethargy, I've buried in a project and just recently
saw the light of day :-)
Yes, you are correct [Tomas], BUT it all depends on the type of
application. Web concurrency is often misinterpreted. The application
I was
On Tue, Jun 30, 2009 at 2:42 PM, Tomas Doranbobtf...@bobtfish.net wrote:
You're doing it wrong.
Don't block app server threads on a remote service if you have a slow remote
service, the only thing that lies down that route is doom and fail.
I don't see the problem. In fact, this was the
Hi all, just my $0.02 here
100 processes per second is not all that impressive for a Catalyst
app. I have tested Catalyst in mod_perl with mod_worker
(multi-threaded apache/perl), in Linux 2.6 and FreeBSD 6.4, 7.x
With mod_worker, you can spawn processes each with an X number of
threads each.
On Apr 30, 2009, at 8:50 AM, Alejandro Imass wrote:
Anyway, the message is that with mod_worker/mod_perl you can spawn
_thousands_ of threads, getting impressive concurrency (without
counting the mutex). We have tested Catalyst applications that handle
_thousands_ of concurrent requests using
My math brings it to about 100 hits per second, rather than 1000, unless
I'm reading things wrong.
9 million page views a day = 9,000,000/(60*60*24) = 104.16/sec
Still an impressive feat for dynamically generated pages.
Peter Edwards wrote:
I was writing a blog entry
Oops. Not paying attention: gets up to nearly one thousand concurrent
requests per second.
Joe Cooper wrote:
My math brings it to about 100 hits per second, rather than 1000, unless
I'm reading things wrong.
9 million page views a day = 9,000,000/(60*60*24) = 104.16/sec
Still an impressive
Yeah, I was reading this the other day. Does anyone know if they use DBIC?
For each query we get we build an abstraction we call our blocklist.
Makes me wonder if they are using their own in house db abstraction?
Graeme
2009/4/17 Joe Cooper j...@virtualmin.com:
Oops. Not paying attention:
On Sat, Apr 18, 2009 at 2:42 AM, Graeme Lawton glaw...@alola.org wrote:
Yeah, I was reading this the other day. Does anyone know if they use DBIC?
Apparently, yes...
...The team which produces the web side server components for BBC iPlayer
is expanding. We use Catalyst, DBIx::Class and TT to
11 matches
Mail list logo
