HackerTrans
TopNewTrendsCommentsPastAskShowJobs

syntonym2

no profile record

comments

syntonym2
·8 mesi fa·discuss
The article missunderstands the futurelock problem. It assumes that the mutex is a "normal" blocking mutex and that the future blocks. This is not the case: The future does cooperate and returns the control back to the `select!` call. The problem is that the `select!` call does not have access to the future that holds the lock, so it cannot make progress.
syntonym2
·11 mesi fa·discuss
In german most job titles can either be masculine or feminine, and the masculine case is chosen "by default". Most job advertisements clarify that persons of all gender are welcome to apply. As the job advertisement is in english, it doesn't really make sense here.
syntonym2
·11 mesi fa·discuss
> The multipart streaming workload is inherently expensive.

Streaming workload is not inherently expensive. The main work is to bring the bytes of the files to the network card as quick as possible, and nearly no computation needs to be performed.

> The cost of generating boundaries and constructing headers scales with request count and payload size.

The only computation necessary to generate boundaries is to ensure that the chosen boundary does not occur in the content, and it seems that the code does not actually check this, but generates a random UUID4. Boundaries and headers are per-file and could be cached, so they don't scale with the number of requests or payload size.