On 01/05/15 00:53, Andrew Stuart wrote:
Hang on I must have done something wrong. I’m now getting this message on the
rump-nginx console:
2015/04/30 22:37:39 [alert] 2#0: *7176 write() to "/tmp/access.log" failed (28: No space left on
device) while logging request, client: 192.168.1.1, server: localhost, request: "GET /static/logo150.png
HTTP/1.1", host: "192.168.1.33"
2015/04/30 23:25:38 [alert] 2#0: *116555 write() to "/tmp/access.log" failed (28: No space left on
device) while logging request, client: 192.168.1.1, server: localhost, request: "GET /static/logo150.png
HTTP/1.1", host: "192.168.1.33"
2015/04/30 23:26:38 [alert] 2#0: *478649 write() to "/tmp/access.log" failed (28: No space
left on device) while logging request, client: 192.168.1.1, server: localhost, request: "GET
/static/logo150.png HTTP/1.1", host: “192.168.1.33"
Odd because I rebuilt by entirely deleting my rumprun and rump-nginx
directories 30 minutes ago and rebuilding. I’m still about 5,600 transactions
per second, which is good but I don’t know why I’m getting the logging errors.
—> ENGAGE BRAIN, 5 MINUTES LATER UPDATE:
Heh, yea, that helps: "put coffee in ignition".
[snip]
location / {
fastcgi_pass 10.9.1.201:8000;
fastcgi_index index.php;
fastcgi_keep_conn on;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME /data/www/$fastcgi_script_name;
}
Hmm, I had to completely remove this bit from my configuration, or nginx
would hang.
Maybe I was doing something else wrong too, since I can't imagine what
it was being used for when requesting static pages, but I wonder if
removing this bit will somehow affect performance.
I now have two Domu configurations, one is ubuntu, one is rump run-nginx. Both
have EXACTLY the same nginx.conf (as shown above) so master and daemon are
turned off on Linux.
Here is the performance stats. Note that with logging completely disabled in
nginx rumprun has jumped up another 1,000 transactions per second.
rumprun-nginx:
2015-04-30 20:00:56, 132031, 19.66, 818, 0.00, 6715.72,
41.61, 9.87, 132031, 0
ubuntu-nginx:
2015-04-30 20:44:34, 153964, 19.93, 954, 0.00, 7725.24,
47.87, 9.86, 153964, 0
I like your hardware and setup more than Martin's ;)
15% performance difference is not *too* bad. I might have enough
compile-time tricks alone up my sleeves to catch up with that. For
example, just avoiding the function calls that "curlwp" currently makes
generally brings ~15% performance boost for in-kernel work. That will
of course not make nginx 15% faster, because it does work outside of the
kernel too, but probably in the 5% neighbourhood.
Quite scientific I think!
Indeed. "experiments are the meat and drink of science"
(bonus points to everyone who knows which game the quote is from)
