Re:Ruby has been fast enough for 13 years
by carsongross on Monday May 16, 2016 @02:50PM
(#11708616)
CPU in the web layer is just not the bounding issue in the vast majority of web apps: network access and query optimization are the bad ones. Where you have big-data like stuff going on, you can and should kick out to a job-processing model based on whatever technology you'd like.
From what I see in our perf logs, a faster string concatenation layer in ERBs would be the place where rails could save a lot of CPU cycles, but it really wouldn't matter except for very large tables, and I use intercooler to keep them relatively small w/ ajax paging or infinite scrolling, depending on the UI.
From what I see in our perf logs, a faster string concatenation layer in ERBs would be the place where rails could save a lot of CPU cycles, but it really wouldn't matter except for very large tables, and I use intercooler to keep them relatively small w/ ajax paging or infinite scrolling, depending on the UI.