https://github.com/aio-libs The set of asyncio-based libraries built with high quality
(but Windows does have a
SO_REUSEADDR constant, and if you use it then it turns on some wacky insecure thing, so on Windows the correct thing to do is just never touch SO_REUSEADDR at all)
*to redis
TCP is not mandatory, HTTP is okay too, however, TCP is preferred
Also I would like to receive files like it does BufferedInputStream, by chunks, not at once
The problem is that I do not know anything about sockets, networking, protocols and Python
@calbot Please explain stream command bytes to redis. I have no idea what do you mean.
I'm a noob in python and dunno how to fix this
I'd suggest installing homebrew https://brew.sh/ and grabbing python3 from there
probably also install a non-broken python2 for good measure, the version OSX ships with is unuseable
@oocydo https://gist.github.com/giefko/2fa22e01ff98e72a5be2 is the first google hit, maybe see what's happening there?
you might want to look into using
sendfile or some other zero copy API to bypass userspace if you want higher performance
I personally wouldn't use Python for this, but I think I'd also just use some existing protocol/servers
but if you basically just want a server that sends raw bytes at any client connecting, that should be straightforward
As there are thousands of blobs and their size might be much more than 100 MB the server needs to support asynchronous I/O
I can manually first detect from where I get the request and then pass to another function/middleware or directly to the handler but I think is not the best approach ;/
You can add something like whitelist to your middleware that would pass through routes like
Or you can use https://github.com/hzlmn/aiohttp-jwt that already have this feature ready for you ;)
/swagger for example.Or you can use https://github.com/hzlmn/aiohttp-jwt that already have this feature ready for you ;)
i need to make a library to call my native async function and the library uses the coroutine-based async function...
it raises a runtime error which says my coroutine was never awaited.
a toy example with just two coroutine functions (native / generator) works well with a deprecation warning... hmmm
Hi folks, I am trying to use aiohttp to do a get request X number of times. I notice every time I run it the performance hugely varies.It takes 10Y seconds sometimes for the work to complete and Y on the very next run. Try again after sometime it goes back to 10Y seconds. I dont see any such variation if i just run with regular requests in a synchronous fashion.
Sorry, I cannot say what's going on your side remotely. Client tracing API can help with analyzing where the time is spent: http://docs.aiohttp.org/en/stable/client_advanced.html#client-tracing
@asvetlov i see the connections are getting created each time for every task, though I am trying to re use the same session. I was assuming that signal would fire only once for sessions getting re used.
async def test_async_order_details1(session):
print("run test order details:{}".format(inspect.stack()[0][3]))
search_index_route = "endpoint".format(api_host)
headers = {'Content-type': 'application/json', "Accept": "text/json", "username": "sample",
"apikey": "sample"}
async with session.get(search_index_route, headers=headers) as resp:
data = await resp.text()
return data
sample client, imagine 100 such testing tasks, one run await resp.text() just takes a lot of time to process with all the requests queued up, then in next run its much much faster than requests.
def test_order_details():
print("run test order details:{}".format(inspect.stack()[0][3]))
search_index_route = "{}/path".format(api_host)
resp = session1.get(search_index_route,
headers={'Content-type': 'application/json', "Accept": "text/json", "username":"sample", "apikey":"sample"})
print(resp.text())