You can't mute your boss, and they're the only messages anyone pays attention to. You can only ignore support for 20 minutes max before your boss starts typing your handle.
Only in terrible office cultures. If everything is urgent, then nothing is urgent. Good office cultures clearly delineate between what needs a person's urgent attention and what can wait for 20 minutes while someone wraps up something they're doing.
I'm working on a Python CLI that uses asyncio/aiohttp to make and process requests to a 3rd party API. Anyways, I ran into the 10,000 socket problem today and ended up using a semaphore, that actually boosted the overall performance. Why is that? Is it just because the CPU is overwhelmed otherwise?
It depends. Maybe you aren't closing the sockets properly (shutdown + close). Or maybe, because of how TCP works, the sockets are stuck in timeouts and don't really close for a long period of time. If its something like that, then your old connections aren't really closing, and new ones can't be created.
Or maybe it's a simple problem of aiohttp performance -- as shown in the blog post, its HTTP parser is a bit slow.
In general, I'd recommend to use a fewer number of sockets and implement some pipelining of API requests.
Are you making all connections within a single session?
Not long ago I saw example here that someone was creating a new session for every single connection. This is not very optimal way of using it. If you use it within same session, aiohttp will make use of keep-alive, which in turn will reuse existing connections and reduce overhead. You also won't need to use a semaphore, since you can define limit in TCPConnector.
Why you had performance issues? As other said, you were making thousands of connections, each socket need to be in TIME_WAIT state for 2 minutes after closing (limitation of TCP, SCTP does not have this problem). So if you use all connections within short time, you'll essentially run out of them. Some people use tcp_tw_reuse/recycle, and that solves this issue, but that makes your connections no longer follow RFC and you might encounter strange issues later on. The advice above should resolve your problem without any hacks.
Don't ask the interviewers what they hate about their jobs. That's easy, everyone hates their job. The best advice here is you should find someplace willing to give you a small token project to work on. Find out for yourself if you hate the place in that period of time.
It definitely depends on the company. Irrespective of the company's dress code, you should look presentable for an interview. You don't have to dress formal to look presentable.
Having run a textbook scanning service (http://www.ptrfy.com/) for a while now, I can say assuredly that keeping master digital copies or the physical processed books is a substantial legal liability.
1) Only an email and password were required to use it (I don't use facebook).
2) It were robust, reliable, and fast; artists without a label or a consistent way of publishing songs shouldn't be a problem. In other words, if I can't rely on this service to track all the artists I listen to, its value significantly diminishes for me.
With that said, I realize you're in beta, and you're off to a great start by addressing a real problem.
Thanks! We elected to use facebook because the user experience is fairly horrid without some initial suggestions, which facebook makes easy through liked artists. The backend for facebook free registration is there though, so if it's that important we can turn it on.
I'll speak with the designer and see if we can get Facebook free registration rolled out. Thanks for the feedback! I appreciate it a lot.
We've just rolled out facebook free registration. It might break the intro a little as it's very tailored to facebook but you should have no trouble registering now.
