<div dir="ltr"><br><br><div class="gmail_quote">On Sun, Sep 25, 2011 at 12:33 PM, Valery Reznic <span dir="ltr"><<a href="mailto:valery_reznic@yahoo.com">valery_reznic@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt"><div>Thanks, Shimi.<br></div><div><br></div><div>I was thinking about Nginx of lightttpd too.</div><div>
While they may have a serious performance benefits I am very short in time</div></div></div></blockquote><div><br>The first time I used Nginx to replace Apache, it took me around 30 minutes to grasp all what's needed to know (which basically is: the default buffer sizes are pretty small; for sites that pass huge cookies / headers, they need to be increased, you might not even need that...). After those 30 minutes, I went from a 12 loadavg and 6GB RAM to 0.5 loadavg with 80MB RAM for my webserver+php ... Nginx is SO MUCH simpler than Apache, the config is *simple*. I do advise you to try it anyways and forget about downtime later. Ever since then, I am not installing any new Apaches, unless it's for things like an SVN server with LDAP authentication, where you need Apache's swissknife. Funny thing is, Apache (from performance/simpleness/resources POV) is probably good for anything *but* simple web serving ;)<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div>With Apache configuration I am a bit familiar bit total stranger to the former two.</div></div></div></blockquote><div><br>So was I :)<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: times new roman,new york,times,serif; font-size: 12pt;"><div>So I think, I'll go with Apache for now and replace it with one of them later if I'll experience performance problems.</div>
<div><br></div></div></div></blockquote><div>Your call :)<br> <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div></div><div>Is it make sense to run this service on non-standart http(s) port?<br></div></div></div></blockquote><div><br>You mean "security by obscurity" ?<br><br>Always remember that one day corporate firewalls will bite you...<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: times new roman,new york,times,serif; font-size: 12pt;">
<div></div><div>Any recommendation about choice MySQL/postgres/whatever?</div><div></div></div></div></blockquote><div><br><br>Most comparisons say "Postgres is better in almost everything" . While that might true, MySQL is probably way more common, and every DB has its own pile of... you know. So for a simple app like the one you're describing, I think the answer would be (contrary to the web server ;)) - "go with what you know best"...<br>
<br>-- Shimi</div></div></div>