top | item 6624309 (no title) blackysky | 12 years ago readFileSync ... not good not good .... nodejs is sexier async ;) discuss order hn newest wcummings|12 years ago node.js is sexier when it doesn't serve stacktraces in production. Plus async files reads still happen in an internal threadpool (one thread per core, hardcoded, IIRC) so it's pretty easy to saturate that anyway, you should be caching static assets. Jare|12 years ago The express framework activates the view cache by default when configured for production, so both problems are actually the same. load replies (1) blackysky|12 years ago you are right but I'll still use async over sync anytime... :) load replies (1)
wcummings|12 years ago node.js is sexier when it doesn't serve stacktraces in production. Plus async files reads still happen in an internal threadpool (one thread per core, hardcoded, IIRC) so it's pretty easy to saturate that anyway, you should be caching static assets. Jare|12 years ago The express framework activates the view cache by default when configured for production, so both problems are actually the same. load replies (1) blackysky|12 years ago you are right but I'll still use async over sync anytime... :) load replies (1)
Jare|12 years ago The express framework activates the view cache by default when configured for production, so both problems are actually the same. load replies (1)
blackysky|12 years ago you are right but I'll still use async over sync anytime... :) load replies (1)
wcummings|12 years ago
Jare|12 years ago
blackysky|12 years ago