Comments for page "Task"

Submitting my solution

Fri, 09 Oct 2009 13:13:56 +0000

After the T/O but anyway :)

4000/5000 req / sec, C2D, no matter cache is populated or not ;)

 Concurrency Level: 100 Time taken for tests: 2.148 seconds Complete requests: 10000 Failed requests: 0 Write errors: 0 Total transferred: 33527250 bytes HTML transferred: 31050000 bytes Requests per second: 4654.52 [#/sec] (mean) Time per request: 21.484 [ms] (mean) Time per request: 0.215 [ms] (mean, across all concurrent requests) Transfer rate: 15239.59 [Kbytes/sec] received

(no title)

Fri, 09 Oct 2009 12:01:16 +0000

Yep, we are digging through solutions — we will try to meet a few authors next week.

Thanks for all the submissions!

(no title)

Fri, 09 Oct 2009 11:16:17 +0000

time out :>

(no title)

Fri, 09 Oct 2009 08:38:31 +0000

Still 82 minutes left for submissions…

(no title)

Mon, 05 Oct 2009 12:42:26 +0000

@terq
I did some tuning to my PHP config, and see the whooping performance of your solution:

+ with empty cache -c 5

+ with pre-populated cache -c 5

+ with pre-populated cache -c 100

I cannot complete the test with -c 100 the cache is not populated, because I am getting apr_poll: The timeout specified has expired (70007) — probably to many concurrent outgoing connections and the thing is not reliable. Also could be Mac-specific. Strange, since I am using only 10 PHP processes to handle the traffic. Should work.

Anyway, nice performance.

(no title)

Mon, 05 Oct 2009 09:41:22 +0000

@michal frackowiak
thx,
but I thought about my script on U testing Environment ;) [starting with clean cache]
(test was mailed from: lp.qret|tkatnok#lp.qret|tkatnok)

(no title)

Mon, 05 Oct 2009 09:32:37 +0000

 ab -n 10000 -c 100 http://127.0.0.4:8081/task.php

+ Show the result

This is on a 64-bit Mac. FastCGI and eAccelerator might be adding some extra boost here, but this setup is new so I did not bother to much tuning. The real application have other bottlenecks.

(no title)

Mon, 05 Oct 2009 09:22:24 +0000

@michal frackowiak

BTW: are you using APC or eAccelerator?

no i dont… (as I know)

could u past me benchmark from U testing Environment 10000/100
I`m so curious

(no title)

Mon, 05 Oct 2009 09:06:05 +0000

Well, not necessarily to anyone particular, but we have solutions that go down below 1 req/s. Honestly I have not seen your solution yet (Piotr did not share it, still waiting), but 80 req/s is reasonable, especially if you machine can do 400 max.

And we have also written our own solutions to this task and we are getting ~ 800 req/s when data is in the cache, on a dual-core 2.6GHz machine. But there are many external factors, hardware and software.

We will go through it, probably together with authors of solutions. No worries.

BTW: are you using APC or eAccelerator?

(no title)

Mon, 05 Oct 2009 08:24:45 +0000

I‘m not sure, is that hint for me…
if so, the higher performance on my PC its a some kind of abstraction :>
ma machine handle ~400req/s on

script ;)
so 80req/s its an magnificent result
Of course in my opinion.

Yes, I could throw out OO api (from main page cache) and use some inline scripting but is it wourth ??

regards

PS. Script was already send to moc.todikiw|rtoip#moc.todikiw|rtoip

(no title)

Mon, 05 Oct 2009 07:33:56 +0000

A small hint is that if

1. the data is already in the cache,
2. you optimize the part of your script that displays the data

you could get a few hundreds of req/s quite easily. But performance aside, we really look much more at overall design (even with such a small task) and elegance of code, which reflects your coding habits.

Benchmark ;>

Sun, 04 Oct 2009 20:03:48 +0000

Hello,

testing environment:
CPU: AMD Athlon 2000+
RAM: 768MB DDR1
HDD: 40GB Seagate Baracuda

My test :D

+ 10000/100 (starting with clean cache) Memcached

Cant make 10000/1000… its kiling my PC :>

Now writeing readme, then pack everything and sending it to wikidot.com

gl ALL

(no title)

Sun, 04 Oct 2009 11:48:49 +0000

@plisken: Featured Sites section is on the very center of http://www.wikidot.com/

(no title)

Sun, 04 Oct 2009 10:47:34 +0000

Just of the curiosity — this "Featured Sites" section is where exactly?

(no title)

Fri, 02 Oct 2009 07:36:07 +0000

Here is a small hint for developers:

The displayed result does not need to be shockingly up-to-date. The information listed on the main page (http://www.wikidot.com) is also cached for some period of time.

It should be more important to create an efficient way of fetching and displaying data and handling dozens of req/s than displaying up-to-date content. This is why we encourage using Memcached.