Blog content was stored in memory and it was served with zero-copy to the socket, so yea, it's way faster. It was before times of php-fpm and opcache that we're using now. Back then things were deployed and communicated using tcp sockets (tcp to rails, django or php) or reading from a disk, when the best HDDs were 5600rpm, but rare to find on shared hosting.

[–] THE_STORM_BLADE@lemmy.world 6 points 1 year ago (1 children)

Couldn't the html be loaded into memory at the beginning of the program and then served whenever? I understand the reading from disk will be slow, but that only happens once in the beginning.

[–] MeanEYE@lemmy.world 3 points 1 year ago

There are plenty of sins people still commit and can commit when it comes to web development. Reading from disk is not the bottleneck. If site is slow most likely it's not the disk read times, database access or anything similar, but silly code that generates the page. It's almost always the code generating the page that's at fault.