> We do not cache "content", as there is not really
> any "content" concept in Wt.
Without proper caching Wt would not be able to scale up well.
There are many central resources like data bases that are shared
between processes.
Otherwise every hit would cause DB access and the application
would die fast. You just have to relay on some shared resource,
you need a way to update cache.
Scaling and creating balanced system is **very** compilcated task,
you just can't tell I'll double the number of computers I use
and the system would increase performance in two times.
>
> > and more then 1 server and share common data like
> session information?
>
> You can deploy a Wt application behind a standard load
> balancing
> reverse proxy that knows how to deal with session affinity
> by matching
> a regular expression on the URL (when using the built-in
> httpd using
> --session-id-prefix). Wt itself does not require shared
> common data
> like session information.
Session is only **one** kind of object that may be shared
between systems -- there are many others like cache and DB.
> For Wt the answer is quite simple: scalability is linear
> except when
> the load balancer would become the bottle-neck (but then
> there are
> other solutions), or when the application logic itself
> contends for a
> common resource.
As I told in reallity you just would not be able to hold "linear"
effect unless your application is really slow.
Another point that scalability is not just how linear can you be
but also how do you perform well. The key is "cache", "cache" and
more "cache".
Its easy to write web application that can hold 10 hits per second
even in PHP. 100 can be done using C++ or using basic caching with PHP
1,000 can be achieven using lot of caching and C++ (and this is
if you have 100% cache hit ratio)/
-------------------------------
But, if you primary marked is embedded system then really you
do not need caching or worry about scaling.
Best Regards,
Artyom
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
