search for: scalibility

Hi All, I am creating on CMS application and there i am providing feature to create document. I have some issue about scalibilty in CMS: 1. How to make size limitation when user is going to create document. 2. How to make size limitation when user is uploading some documents. 3. How many documents can we create in CMS their is any limit?? 4. How to handle database scalability for CMS

The question was posed: "incomming calls for 45 or so people that will call in 3 or 4 time each day during (approx) normal business hours" The comment was made (taken out of context): "The quick math says that 45 people with 4 calls is 180 calls a day. In a 8 hour day you have 480 minutes. From 480 minutes 1 port could handle the load if the call was under 2.5 minutes long and

Hello all: Thank you for taking the time to read this post. Background: I am a new user to IVR systems and asterisk. I have been tasked with helping to set up a system that will only handle IVR (eg no PBX functions) incomming calls for 45 or so people that will call in 3 or 4 time each day during (approx) normal business hours. We have started to look at the Ivrs perl module from

...5mbit - NIC-4: 3mbit Just to summarize, ALL I''m trying to do is limit the bandwidth on each NIC (ingress & egress) whether it is 10/100/1000Base-T. Right now I am using a Cisco using rate-limiting which is very simple. I''d like to perform this task on Linux box for easier scalibility and as a backup. Thanks for your assistance! -JGR

The original implementation utilies select(). In Linux select() typically supports up to 1024 file descriptors. This can be a problem when user tries to boot up many guests. Switching to poll() has minimum impact on existing code and has better scalibility. Up to 8192 file descriptors are supported in the current implementation. Signed-off-by: Wei Liu <wei.liu2@citrix.com> --- tools/console/daemon/io.c | 90 +++++++++++++++++++++++++-------------------- 1 file changed, 50 insertions(+), 40 deletions(-) diff --git a/tools/console/daemon/io...

...http://codeforpeople.com/lib/ruby/acgi/ i think it''s a potentially powerful idea. if you know how to make it faster, please do so and send in a patch. at this point only a factor of 2x is need to close the gap on fastcgi. at this point the emphasis is on making it as fast as possible. scalibility and portability might come next. good luck. -a -- in order to be effective truth must penetrate like an arrow - and that is likely to hurt. -- wei wu wei