{"issue":{"created_at":"2011-12-09T13:36:18Z","state":"closed","updated_at":"2011-12-11T02:10:06Z","comments":1,"user":{"gravatar_id":"0ceb885cc3d306af93c9764b2936d618","id":161683,"url":"https://api.github.com/users/joehoyle","avatar_url":"https://secure.gravatar.com/avatar/0ceb885cc3d306af93c9764b2936d618?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"joehoyle"},"body":"Hey,\r\n\r\nAmazing work by the way, very easy to setup and use!\r\n\r\nI presume the bees are using `ab` to hit the requested URL. This is good for testing the response of one URL, however as we use Varnish - it's fair to say a single URL can handle a lot of req/s, as Varnish is soo damn fast! \r\n\r\nWhat would be great would be for the benchmarking tool to also request all the assets on the page. I am not sure if there are any bench tools that will do this, I presume ab doesn't support it. Being able to do this would really help in being able to isolate varnish_miss requests for a given URL, as that's a lot closer to how real world traffic would be.\r\n\r\nAny ideas / thoughts?\r\n\r\n","assignee":null,"id":2501501,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"number":23,"title":"Support for hitting on-page assets","html_url":"https://github.com/newsapps/beeswithmachineguns/issues/23","closed_at":"2011-12-11T02:10:06Z","url":"https://api.github.com/repos/newsapps/beeswithmachineguns/issues/23","milestone":null},"action":"created","comment":{"created_at":"2011-12-11T02:10:06Z","updated_at":"2011-12-11T02:10:06Z","user":{"gravatar_id":"5fa54fdf60acfa1dd99d4d5f68ddbdce","id":33046,"url":"https://api.github.com/users/onyxfish","avatar_url":"https://secure.gravatar.com/avatar/5fa54fdf60acfa1dd99d4d5f68ddbdce?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"onyxfish"},"body":"Yeah, this is something that would be really useful, but is outside the scope of the bees. There are some advanced load-testing tools that will spider a page and give you a more realistic distribution of requests. I think jmeter is the canonical one. Such tools tend to be a lot of overhead to configure and best suited to big, enterprise deployments (where somebody is specifically paid to configure them). I'd love to have an easier tool for doing that sort of testing, but bees ain't it.","id":3095186,"url":"https://api.github.com/repos/newsapps/beeswithmachineguns/issues/comments/3095186"}}