alexginzburg

Alex from Seva here: We are actively building integrations with the most popular services. Here is the list of the active integrations: Gmail, Google Calendar, Google Drive, Dropbox, Box, Slack, Confluence, Jira, Clubhouse. As for the pricing, we are currently offering a free trial. After the trial the price is $10/month

First, the article starts talking about the accept() and thundering herd but the example shows use of the select().

Second, accept() goes over a queue of the established connections created by a listen() call

select() and accept() are meant for different things. selec/poll/epoll/kqueue work with a list of file descriptors to detect I/O, accept works with a socket.

It seems that the author is slightly confused. Description of the thundering herd is mostly correct. Initially it referred to multiple processes calling the accept() on a single listen socket, it used to cause all processes to wake up. This has been fixed a long time ago. Currently multiple processes blocking on the accept() on a single listening socket works in a round-robin fashion (AFAIK). Calling select() from multiple processes on a single fd, should wake all the processes up when IO comes in. This is a documented behavior.

--Edit--

s/write/IO/

Could you elaborate what redis configuration could've caused this?

we are in the same situation. Early morning today found one host with a high cpu usage. Turned out it was running `./yam` process as a `redis` user. I shut the host down for now. Before shutting it down I did a strace and saw json stream clearly stating that it is a monero app. Looks like the cpu spiked about 12 hours ago. We do have redis on a host but it should be behind the iptables rules. Other hosts look ok.

Overbooking in the hotel industry is a normal practice. Cancellation rate is pretty high. Hotel Tonight deals with the last minute inventory, overbooking here would result in unsatisfied customers. I worked for an online hotel booking site in the past. We had integrations with multiple GDS and channel managers, SynXis (Sabre) was one of them. SynXis was not the fastest or most accurate when it came to inventory. SynXis had some ridiculous throughput limitation to query for availability, luckily we did not have to rely on that API. I can't speak about original Sabre technology since I haven't used it myself.

using a system package manager does not mean that one needs to use a distribution's (debian, ubuntu, redhat, gentoo, arch, etc) mirror to pull the package, it does mean that you use an OS provided tool to manage all software on your machine.

- It does mean that the common libraries are installed once - conflicts between common libraries are more transparent - System tools make sure that package stays up-to date