From 76e782f836405d2c19af9aba73392ff3f2df6822 Mon Sep 17 00:00:00 2001
From: "Steinar H. Gunderson" Last updated March 21st, 2008 Last updated July 21st, 2008pr0n FAQ
- So, what is this pr0n thing anyway?
@@ -54,7 +54,7 @@
so the next time somebody views the same images in that resolution,
it will be snappy as usual.
Because it didn't fit my needs, and the same goes for all other systems I've seen. I wanted something no-nonsense that would work for my @@ -78,7 +78,7 @@
pr0n currently runs on an Athlon 64 X2 3800+ with 4GB RAM and ordinary +
pr0n currently runs on an Intel Q9450 (quad-core 2.66GHz) with 8GB RAM and ordinary SATA disks. (The server does a lot of other stuff besides running pr0n, of course.) pr0n itself is a custom-made system by myself, tightly coupled into Apache 2.2, Debian lenny (ie. âtestingâ).
The Perl modules aren't really that big â we're talking about only - approx. 2800 lines of code (of which ~25% is the WebDAV part; I should + approx. 3300 lines of code (of which ~25% is the WebDAV part; I should really make that a bit cleaner once). Most of the real work is done by the software on which pr0n builds on.
At the time of writing, approximately 115GB of image data (that is, over - 67000 different images), plus cache, plus metadata in the SQL database. +
At the time of writing, approximately 140GB of image data (that is, over + 72000 different images), plus cache, plus metadata in the SQL database. (These numbers are growing rather rapidly, so they could be outdated at any given time.)
-- 2.39.2