Search the Community
Showing results for tags 'scalability'.
Found 2 results
Hi, I've been testing out Revive and I'm finding that I need to be able to scale my cluster horizontally as my traffic grows. I came across a few old OpenX blogs which mentioned configuring OpenX for 'Distributed Statistics'. Is this possible with Revive ? And can anyone point me in the direction of any docs which show how to set it up ? Thanks Keith
Hey guys, I'm having a hard time setting up a large scale setup for revive 3.0.3. I'll explain what I'm doing and see if you could help me out on scaling things out or with something that I'm missing. My current architecture follows the bellow setup: 2x Portal - (EC2 m1.large) = ~ run smooth (30% cpu) from 0-5000 visitors (google realtime) or ~ 600 visits from nginx_status/fpm_status pages PHP+FPM with pm.dynamic and pm.maxchildren 512, with sysctl configs effective setted. no OPCache setted yet. 2x Revive - (EC2 m1.large) = ~ run critical and stops PHP+FPM with pm.dynamic and pm.maxchildren 512, with sysctl configs effective setted. no OPCache setted yet. http://imgur.com/0D7kgvd 1 RDS - (db.m1.xlarge) = was running high on connection count mostly because table locking, solved after migrating from MyISAM to InnoDB, and LG caching on nginx (so no visits/impression count) just clicking Runs the queries for the ad server to work, the picture bellow shows the situation for the setup http://imgur.com/1e86Gqe The PHP portal makes server side requests for the adserver ones, one of the main pages has at least 90 banners, so when it opens, it'll spawn as much as 1x90 multicurl per visit for each view. After that the client side will show the banners correctly and also make more 90 request for the LG's beacons. The problem now is to scale that thing out, am I missing something? how to run such a massive delivery/impression log with RDS? should I try differently? Thanks in advance for the help and please, make your self comfy for asking for more configs or any other questioing.