5

Would a PHP application benefit from being served from a RAM drive?

view full story
linux-howto

http://serverfault.com – I am in charge of hosting a PHP application that is large and slow, but easy to scale. The application is entirely static, with writable disk storage needed. We've profiled the application, and the main bottleneck appears to come from loading the application and not the work the application does. The application is not CPU-intensive, although it does use a fair amount of memory (think Magento). Currently we distribute it by having a series of servers with the same PHP files on their hard drive and a load balancer in front of them. Easy but expensive. I've been reading about RAM disks and the (HowTos)

u85500's picture
Submitted by u85500 on 07/08/2012 – Made popular on 07/08/2012

Stories similar to Would a PHP application benefit from being served from a RAM drive?

32 bit app on aix 6.1 51 weeks 5 days ago

We have our in house developed software running on AIX 6.1 (6100-06-06-1140). The application is a 32 bit application and the operating system is 64 bit. We are running this application without any issue on AIX 5.3 32-bit on P5.

Hello first let me apologize in advance if this is a repeat or trivial question as I am not very experiences in the webserver/IIS world.

I have recently set up an asp.net web application on IIS 7. The application has its main application and in one of its sub directories an additional application which happens to be a message board.

I need to model a Rails application that does video processing using Amazon AWS resources (EC2).

Application allows users to convert videos. Videos are uploaded by users. Right now it is running on one instance, but I see the need to scale up / change things.

Question:

Does it make sense to create two instances:

1) Application front-end.

I have an ASP.NET 4.5 (Web API) web application hosted in IIS on Windows Server 2008 R2.

We have an application that is IP restricted via an .htaccess file. Another application is used to request access and updates the .htaccess with the users IP for a period of time.

The current server configuration uses just one box, so it is easy to update the htaccess.

Let's say I have a fully working, load-balanced application server environment.

All servers have to fail-over gracefully. It's relatively easy to do with the application servers, but how can I achieve fail-over with the front load-balancer?

Can I have multiple load-balancers listening on the same IP and port? Do I have to run a new one as soon as I detect the old one died?

I work in a company that has a slow large WAN covering many different locations on all continents.

Releases of a particular internal application consist of DLLs and data files that can cumulatively top 100 MB, and there is talk of the application growing.

I currently have 2 servers on Which nlb and application pools are running .Since the nlb doesn't recognize, that if an application pool has failed, it sends the request even when an application pool has stopped.

So, I was thinking of Application Request Routing(ARR).

Ftp server Perfomance 25 weeks 1 day ago

i have a ftp server and asp.net application deployed (iis) on the same machine the ftp server is on F drive and the application is on C drive hosted on iis . the application is used by 500 users daily through internet explorer.