X-Git-Url: https://git.sesse.net/?p=pr0n;a=blobdiff_plain;f=files%2Ffaq.html;h=c07aa567d5ddd8a422f6300db1cf0dffb0bfdf1a;hp=4d4612afd68af33e2cb5df5a5c9d82be1432c054;hb=400a1bbb95bf6837807e2819825cddd00c219cf1;hpb=4835316881ebf76c404cc721b1d8bc5e5ab39248 diff --git a/files/faq.html b/files/faq.html index 4d4612a..c07aa56 100644 --- a/files/faq.html +++ b/files/faq.html @@ -9,7 +9,7 @@

pr0n FAQ

-

Last updated March 23rd, 2009

+

Last updated November 20th, 2015

So, what is this pr0n thing anyway?

@@ -75,37 +75,37 @@ Also, it has dynamical rescaling (of good quality — proper, sharp thumbnails, no crappy nearest-neighbor scaling) of both thumbnails and images (most client-side scaling sucks quality-wise, unfortunately), - an easy-to-use WebDAV-based upload + an easy-to-use HTML5 upload interface, cache awareness and in general good performance (being a set of persistent, optimized Perl modules; I've seen it throw out over 300 - hits a second even without the Squid in front, but I won't guarantee it + hits a second even without the Varnish in front, but I won't guarantee it would withstand a Slashdot attack ;-) ). Also, it has quite OK skinning capabilities, so it's able to adapt into different designs quite easily.

What hardware/software does it run on?

-

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, - mod_perl 2.0, - ImageMagick 6.x +

pr0n currently runs on two Intel E5-2650v3 (2x10 cores at 2.30GHz) with 64GB RAM and + SATA disks, with some SSDs in front for cache. (The server does a lot of other stuff besides running pr0n, of + course.) pr0n itself is a custom-made system by myself, + a PSGI + app server running under Starlet + behind Varnish 4.1, + using ImageMagick 6.x (as well as various other Perl modules) and qscale, using - PostgreSQL 8.4 as the back-end + PostgreSQL 9.4 as the back-end database for metadata et al. The base operating system is - Debian jessie (ie. “testing”).

+ Debian jessie.

The Perl modules aren't really that big — we're talking about only - 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 + approx. 2600 lines of code. Most of the real work is done by the software on which pr0n builds on.

How much data is there in there, anyway?

-

At the time of writing, approximately 250GB of image data (that is, over - 88000 different images), plus cache, plus metadata in the SQL database. +

At the time of writing, approximately 720GB of image data (that is, over + 195000 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.)

@@ -129,26 +129,13 @@ the images :-) If you really have a novel or cool feature, feel free to contact me (see below).

-

Is the upload WebDAV server RFC-compliant?

- -

Unfortunately, no. When and if somebody makes a sane framework for - making WebDAV servers I can use, it probably will, but ATM it's just - too much work for what I need it for. It would be a lot easier if - I only had to support WebDAV level 1, but due to silly restrictions - in Mac OS X' WebDAV client I have to support WebDAV level 2 as well, - and, well, most of that is faked. ;-) In addition, there are multiple - minor features in the system (like autorenaming files on name clashes) - that just aren't easy to adapt to WebDAV. The WebDAV service is - restricted, though, so I guess rather few people will get hurt just - because I'm not fully compliant ;-)

-

How do I get in touch with you?

Try e-mail, or reach me on IRC as Sesse on EFnet, IRCnet, Freenode or OFTC.


- +