Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If I/O were the bottleneck then that would be the case with or without a lock, wouldn't it?


It depends on what has to wait for the IO to complete. ETW, for example, is a Windows-wide event framework and it would be untenable for everything using it to wait on the file IO of everything else making use of it. So, it has a solution that makes use of locks but nothing ever has to wait on file IO.

File IO is always expensive, the trick is always in how you work around that.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: