Glyph@dalias @mcc @0xabad1dea the reality of fork() is that the CoW costs are ~always _far_ more significant than system designers account for. profiling pretty much anything that calls fork() in a real-world context (apache, or anything that calls fork() in a refcounted runtime (python/ruby/perl/PHP/etc)) shows just an appalling amount of post-fork faults that copy way more memory than "should" be touched
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.