fastcgi vs wsgi

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAEBAgAGBQJQH+q9AAoJELhxXPVStcgQvzYP/j8eqYtv1O7oLEP28EwM7Uho
tQq4Jwl9sU6lXvMWoZ+B4oVg5EoiUfFdf60YG3MmVmc6GLyJm0VdIEVLzXza+qeJ
RWWfZ4QBwTiHSsBXpHXw9QaTsNs0lXVPewfzLPgLGH2h8QbIpAkMPpPa31n3SpZN
ogoRr8y3xc6TLvHPubyJElk25aQI4qmK6SKtSevjMHve3kKL3oV2l1nEORuQHnja
yjW2vn97QzaFjo0HrbVTI00/uaUj7bXYiax/k5M6qO6USZIYcL7I0EW17gzEcCOS
n8+0eOUWtiHkWsvFa6jHJ1sDdHPDw9CU4f2mip4/MmtSEE0q2Dva1xdNWB5jocz0
L/nO4bi0NFsIC9i8unAoo1NRfGxUPejjabuS9wTlmh2LDd04XZJEFFRG3WBWZQkG
dZh7npBxKiS28zR52/+f/CnNL8nkUejTCULIMxSuxwKvKqIWM2pMhzI1PUJnL94Z
dX8FkRiiiBJzZGaZ90JxjzZeYgeMqaoEJRY9e6P8s1KxAjljkxWZ5hQA2rQcU55U
bHM1OtE1DB7YZYVlueiV61sgfPtJTSzA9VR2yc2fXrS6mt2lLcKgvwcxrjXMGfm2
tk9LELO4TbAltUhdXARxag2qu/2xVGZdCiFWeHBAedQi/tD0v+3HLUEBUwCirsN9
/VhbkYxR/4X6bLsbJ+6Q
=mAV1
-----END PGP SIGNATURE-----
Hello,

At the moment I (have to) run 3 php sites in a tight memory environment
using lighttpd server & php-fpm and I'd like to move one php site (for
the beginning) to django cms (mezzanine) and wonder what is the impact
of running django app with fastcgi vs wsgi? how they compare
memory-wise?

Considering that the server has to serve 2 PHP sites via fastcgi, would
using fastcgi for deploying Django be better option memory-wise instead
of serving Django app via wsgi?

If wsgi option is better option, what would be optimal wsgi server
memory-wise: uwsgi, gunicorn, fapws..?


Sincerely,
Gour

--
The embodied soul may be restricted from sense enjoyment,
though the taste for sense objects remains. But, ceasing
such engagements by experiencing a higher taste,
he is fixed in consciousness.

http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810