I will definitely consider at Yahoo Boomerang. But currently, Episodes still looks better. Episodes doesn’t have support yet for the Web Timing spec, but that can easily be added. Boomerang appears to be designed to run tests to measure the potential performance: it measures 1) the RTT and 2) bandwidth and latency. Episodes measures the actual performance of loaded pages. And that’s what matters most.
So, in their current incarnations:
- Episodes measures actual page load times
- Boomerang measures the network connection
For my thesis, I absolutely need actual page load times. But the information that Boomerang provides, can also be very useful; it can help in deciding where the largest gains can be achieved.
If feasible, I’ll try to help in combining both :)
I will definitely consider at Yahoo Boomerang. But currently, Episodes still looks better. Episodes doesn’t have support yet for the Web Timing spec, but that can easily be added. Boomerang appears to be designed to run tests to measure the potential performance: it measures 1) the RTT and 2) bandwidth and latency. Episodes measures the actual performance of loaded pages. And that’s what matters most.
So, in their current incarnations: - Episodes measures actual page load times - Boomerang measures the network connection
For my thesis, I absolutely need actual page load times. But the information that Boomerang provides, can also be very useful; it can help in deciding where the largest gains can be achieved.
If feasible, I’ll try to help in combining both :)