| T O P I C R E V I E W |
| MarcelG |
Posted - 06 January 2010 : 05:55:28
I'm trying to see how Oxle handles a "large" load.
For that I've opened up a special topic: http://oxle.com/topic/6127.html
I'd really appreciate it if you guys could participate in it.
Participating is easy: visit the topic, reply with the parsetime and that's that. 
Oh, and you can win an übercool Q.Oxle account with lot's of diskspace and bandwidth.  |
| 5 L A T E S T R E P L I E S (Newest First) |
| taropatch |
Posted - 06 January 2010 : 11:42:14
I missed the test but happy to help if I am available for the next one. |
| Etymon |
Posted - 06 January 2010 : 11:33:51
I'll plan on being there for the test and the prize  . |
| Etymon |
Posted - 06 January 2010 : 11:31:54
You mentioned the contest ... ask for interested parties to contact you (so you know how many to expect) ... set a date and time (to get them all there at the same time) ... create a place for them to meet (like you did the first time), write up a post explaining the details of the contest and provide some reading material introducing the Q.Oxle account and why it is übercool (to give folks something to do while the test is being conducted) [perhaps even a tour of some übercool public accounts] ... maybe provide them a quiz to take to test their comprehension of the stress test and the Q.Oxle offer (again something to keep them entertained during the test) ... remember to send out a thank you to all of the contestants.  |
| MarcelG |
Posted - 06 January 2010 : 11:21:24
The previous one (back in 2008) was indeed against the Access DB, and now I'd like to find out how Oxle (being on SQL) can handle such loads.
However, the test has already ended, and we didn't get more than 28 concurrent users online at any given time.
I'll have to find a way to get more people from all over the world to participate at the same time....going to get out my thinking cap and come up with a cunning plan. |
| Etymon |
Posted - 06 January 2010 : 11:12:02
I am supposing the stress test was against an Access db. Are you going to resume it against the new MS SQL db? |
