large numbers of members
webdesign | Posted 10:40pm 6. February 2008 Server Time |
There is this website that I am creating for a client.
The potential to have 5,000 + members logged in at the same time is there.
1.) What is the largest number of members (people who will be logging in) that you have ever had?
2.) Are there any potential problems with the members updating the a specific database at the same time?
I have created other website where this was not an issue. But I want to avoid problems.
Thanks in advance |
probinu | Posted 8:44am 7. February 2008 Server Time |
It depends on what technology you will be using. If you are using .NET and SQL server you should be fine as long as you code accordingly. (I don't really know what you are attempting to do but 5000 users is not a lot)
Access would not be a good solution for a database.
webdesign | Posted 7:22pm 7. February 2008 Server Time |
What are some of the flaws of using access?
webdesign | Posted 7:38am 10. February 2008 Server Time |
What are some of the flaws of using access?
anybody know?
katy8439 | Posted 10:54am 11. February 2008 Server Time |
Sometimes with access if you get a large number of users updating at the same time the .ldb file gets locked and kicks you out of the database, then it's a real swine to get rid of it.
Apart from that I think you'll be okay.
probinu | Posted 12:58am 11. February 2008 Server Time |
Access is meant for a personal database. If you have 5000+ members updating a database then I assume you will be storing large amounts of data. Access after time will not hold as much data as a SQL server for example and the performance of the application will suffer.
katy8439 | Posted 2:56am 12. February 2008 Server Time |
You can have an access database of a gig easy. As long as it's well designed it shouldn't be a problem.
webdesign | Posted 8:26pm 15. February 2008 Server Time |
how about if I have about 1000 people updating the database?
Could things be text file driven? instead of MS Access?
katy8439 | Posted 6:21am 21. February 2008 Server Time |
That's a lot of reading/writing to the server - I'd steer clear of text files.
Still don't think you'll have a problem with access at all :)
mp3cdman | Posted 5:33pm 6. March 2008 Server Time |
Access can only handle a maximum of 10 concurrent connections before it gets screwed up..
here's just one article detailing various peoples experiences. http://www.15seconds.com/issue/010514.htm
It all depends what you need to do though...
If you can cache some of the queries somewhere (filesystem, Application Object etc) then you can get a massive improvement but then you lose a lot of the active qualities that using a database give you.
If 5000 people all access the database at teh same time (or say even 1% which is more reasonable) then Access WILL fail...
go with MySQL and ASP if you cannot afford a MSSQL database... you'll get much better performance and guarantees that the site won't fail catastrophicaly..
mp3cdman ;-D
Reply to Post large numbers of members
|
|
|
