Find performance bottlenecks

uber / eight-track

Record and playback HTTP requests

MIT License

70 stars 18 forks source link

Find performance bottlenecks #16

Open twolfson opened 10 years ago

twolfson commented 10 years ago

While #14 is a step in the right direction, the benchmark of 800ms for 100 repeated requests leaves me wanting more. We should add some timing logs to each function run in the test suite.

Off the top of my head, some more possible gains might be:

Key generation (try to use a better serializer)
- https://github.com/isaacs/sigmund
Caching of generated keys (avoid md5 if it is too slow)

twolfson commented 10 years ago

I thought I wrote this down but I guess not. Consider using object-hash for our key serialization:

https://www.npmjs.org/package/object-hash