3 ms·
1. There's various low-hanging performance fruit that hasn't been picked. 2. Python has several different ways to do concurrency (because they evolved over ~25
by wmf 7y ago
1. There's various low-hanging performance fruit that hasn't been picked.
2. Python has several different ways to do concurrency (because they evolved over ~25 years) that shouldn't be mixed but it's very easy to accidentally mix them.
3. Binary RPC (e.g. gRPC or Thrift) is more efficient than REST.
- hermitdev 7y agoI have a lib that queries quant data from a internal webservice. We have to break up large queries into smaller ones (like 4 days at a time). We currently use multiprocessing to get some parallelism. I prototyped using aiohttp. It was nearly an order of magnitude faster using a single thread. Unfortunately, cant use aiohttp because it doesn't do Negotiate/SSPI auth, which aiohttp doesnt support.