Sorry, but I just don't see the need for transparent failover in most
cases. I don't believe many web applications have unsaved state over
more than a few requests. So yes, you lost a server and you have to
login again, but so what? It's not like it's going to happen very
often to a single user.
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great optimizing points?
Don't bother guessing. Attach a good profiler and discover where the
bottlenecks *actually* are. Then fix them, one by one. (Afterwards,
tell us
Hello,
as of my experience there are two performance areas:
- page/page part rendering performance - garbage collection and custom
algorithms.
- page delivery performance - caching.
Regarding the former one:
- custom algorithms: By these I mean all software pieces implemented on
request of the
Etc. There's a ton more questions to ask, but I'm sure you'll figure
that out in the context of your project :-) One of the most important
decisions you'll make is what parts of your application (maybe even
everything) you'll set up to be stateless and bookmarkable. Keep in
mind that even
thanks for the pointers..
Ryan Sonnek wrote:
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Hi Guys
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great optimizing
On 16 jul 2008, at 04:49, Ryan Sonnek wrote:
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez
Wael
[EMAIL PROTECTED] wrote:
We are having the potential fun of running a site with around 1
million
users, and a lot more over time. What could be great optimizing
points?
Daan van Etten wrote:
On 16 jul 2008, at 04:49, Ryan Sonnek wrote:
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great
On 16 jul 2008, at 09:54, Nino Saturnino Martinez Vazquez Wael wrote:
Daan van Etten wrote:
On 16 jul 2008, at 04:49, Ryan Sonnek wrote:
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez
Wael
[EMAIL PROTECTED] wrote:
We are having the potential fun of running a site with
It is exactly the opposite: keeping state serverside increases
performance. It makes it more expensive to scale out, but that is
about it.
Keeping state readily available at the server ensures you don't have
to send it across the wire, or have to reconstruct it at the server.
It consumes memory,
Hi Martijn,
On 16 jul 2008, at 10:19, Martijn Dashorst wrote:
It is exactly the opposite: keeping state serverside increases
performance. It makes it more expensive to scale out, but that is
about it.
Can you elaborate a bit on your first statement? You need a lot of
data-juggling for many
For wicket keeping server state gives you more performance, except maybe the
serialization penalty which is an overhead.
But if you have enough memory for your clients (the expense to scale out) it
is way faster
If you use bookmarkable/stateless pages then everything has to be
constructed on the
IMHO whether state at the client helps hugely depends on the amount of
pages the user works with.
If the user hardly ever leaves that one single page, keeping state on
the client will help performance, provided the server does not need to
keep a copy of (all) that state. The latter deviates
On Wed, Jul 16, 2008 at 10:33 AM, Daan van Etten [EMAIL PROTECTED] wrote:
Can you elaborate a bit on your first statement? You need a lot of
data-juggling for many clients, so I'd love to learn why it gives higher
performance at the server.
What is this data juggling you talk of? If you use
On 16 jul 2008, at 11:34, Martijn Dashorst wrote:
On Wed, Jul 16, 2008 at 10:33 AM, Daan van Etten [EMAIL PROTECTED] wrote:
Can you elaborate a bit on your first statement? You need a lot of
data-juggling for many clients, so I'd love to learn why it gives
higher
performance at the server.
Hi,
Everybody think happy thoughts, flowers, waterfalls, idle servers :-)
On Wed, Jul 16, 2008 at 11:34 AM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
On Wed, Jul 16, 2008 at 10:33 AM, Daan van Etten [EMAIL PROTECTED] wrote:
In my opinion it depends on your use case, but in high-load
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great optimizing points?
Million users per week/ month/ year/ decade? ;-)
Answer these questions for yourself:
1) On average, how many concurrent sessions will there be
Thanks for your mail:)
Eelco Hillenius wrote:
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great optimizing points?
Million users per week/ month/ year/ decade? ;-)
We actually discussed this today:)
Answer
Hi Guys
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great optimizing points?
We have looked at these things
* Detachable models (not sure if it makes anything run faster, just
that it keeps the memory
Nino Saturnino Martinez Vazquez Wael wrote:
* Clustering(simple web server clustering with apache
http/loadbalancer/tomcat)
o Would Jetty be better?
Terracotta?
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
Yeah, will look into it.. And thanks! :)
Erik van Oosten wrote:
Nino Saturnino Martinez Vazquez Wael wrote:
* Clustering(simple web server clustering with apache
http/loadbalancer/tomcat)
o Would Jetty be better?
Terracotta?
--
Erik van Oosten
Hello,
Could you share with us the link to the website ? I don't think it's
jayway.dk.
And I was wondering what your DB is...? Are you using Hibernate?
I think everyone would appreciate you sharing all the information you can
about the design, etc. Most of us are hoping to build a website just
The site is not public yet, as we are in beta testing currently. I'll be
happy to give out links once we go public:)
Cristi Manole wrote:
Hello,
Could you share with us the link to the website ? I don't think it's
jayway.dk.
So true:)
And I was wondering what your DB is...? Are you using
On Tue, Jul 15, 2008 at 8:54 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Hi Guys
We are having the potential fun of running a site with around 1 million
users, and a lot more over time. What could be great optimizing points?
We have looked at these things
*
23 matches
Mail list logo
