This is farily simple. No big deal. DAL can be switched to PostgreSQL
without having to do anything other than change the line at the top of
the db.py file in MODEL.

This sounds like a school course registration system.

Definetly use the APACHE + WSGI. Also, use caching as much as possible
for your databse. Shouldn't be a problem at all.

Good luck, and let us know how it goes.



On Nov 23, 10:36 am, harshit agrawal <harsh.agrawal2...@gmail.com>
wrote:
> This is a fact.
>
> Sir I am almost done with all the queries in my project using the
> default sqlite and now I want to put the portal on apache server. How
> can we do this?
>
> On Nov 23, 12:47 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > On Nov 23, 11:36 am, harshit agrawal <harsh.agrawal2...@gmail.com>
> > wrote:
>
> > > But sir my portal will start at a specific time and around 200-250
> > > users will login at the same time then the system may hang.
>
> > Is this an assumption or a fact?
>
> > > Also there is a file named options_std.py, in this file what does
> > > 'no_of_threads' means....
>
> > that is the number of concurrent threads with wsgiserver. It should
> > not be relevant in a production environment.
>
> > In a production environment you should use apache2+mod_wsgi and let
> > Apache deal with concurrency and serving static files. You should also
> > use postgresql (or other database) not the default sqlite. sqlite
> > always locks the entire database on every request.
>
> > You can read more on this in chapter 11 of the book and the source of
> > this script:http://www.web2pyslices.com/main/slices/take_slice/29
>
> > Massimo
>
> > > reply as soon as possible
>
> > > Thank You
> > > Harshit
>
> > > On Nov 23, 10:15 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > It really depends on many issues. 200 users are not going to make 1
> > > > request/second but more like 1 request every ten seconds each or less.
> > > > That means you need to handle 20 requests/seconds.
>
> > > > On my laptop an average dynamic page takes ~20ms, and that means 50
> > > > requests/second. This means I can handle 200 current users on my
> > > > laptop.
>
> > > > The bottleneck is always database access. It really depends on what
> > > > those users do with the database.
>
> > > > Massimo
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to