Ted,
From my tech, you asked for it, here goes :-)
Most of the configuration is in our help files. Go to:
http://bigfish.solveda.com/help/index.htm -- checkout the "General
Guides" (Deployment) on the right hand side. Nothing special is
needed to get it working, though we've made some specific changes
since setting it up.
The most important issue is memory. Apache is not much of a concern.
On BigFish/OfBiz We use 5GB for Xms and Xmx and 1G for MaxPermSize.
That uses up to 80% of total system ram. (up to 6GB out of 7.5GB
available)
For MySQL innodb_buffer_pool_size is set to 5376 MB
We use mysql's recommended 70% of available ram for a dedicated
mysql server.
The first server running apache connects to Bigfish using the
standard mod_proxy_ajp settings. There's no special configuration.
The second server running bigfish connects to the DB by specifying
the DB server internal IP address (provided by Amazon) in the
database.server property in client-deployment.properties before
building.
OFBiz settings we change are:
in framework/base/config/cache.properties
changed product.content.rendered.expireTime to 600000
in framework/webapp/config
changed:
stats.enable.* to false
stats.persist.* to false
except
stats.persist.visit=true
stats.persist.visitor=true
Amazon specific configuration:
Make sure all servers are set up in the same availability zone.
Amazon provides the best connectivity between instances in the same
zone, (at gigabit speeds) with no data charges for data transferred
between servers using the internal IP addresses they provide - so
communication between the 3 servers doesn't incur any charges.
Correctly set firewall settings in the EC2 dashboard under Security
Groups
You'll need ssh open on all servers for managing the servers. If
possible, only allow ssh from your own IP (if you have a static IP
from your ISP).
Aside from that, ports 80 and 443 should be open publicly ONLY on
the apache server
The AJP port should be open to allow access only from the Apache
server and to the Bigfish Server
The MySQL port should be open to allow access only from the BigFish
server and to the MySQL server
No other incoming ports need to be open, so it's best to keep them
blocked.
Using linux, regardless of where it's hosted, you'll need to open
the correct ports in iptables on each server (open 80 and 443 on
apache, ajp port on bigfish and so on).
HTH
Nick
On 1/20/2014 10:49 AM, Ted Byers wrote:
On Mon, Jan 20, 2014 at 10:47 AM, Nick Rosser<[email protected]> wrote:
No ... just configuration. I can get details from my tech if you're
interested in the specifics.
Yes, I am actually. I'd appreciate that.
Thanks
Ted
On 1/20/2014 10:45 AM, Ted Byers wrote:
Thanks Nick,
Did you have to do anything different in the OFBiz codebase to have it
work
on this sort of server cluster?
Cheers
Ted
On Mon, Jan 20, 2014 at 10:19 AM, Nick Rosser<[email protected]>
wrote:
Ted,
The site is hosted on the Amazon Cloud. It's a 3 server configuration,
all
have 2 virtual cpu cores (amd64) with 7.5Gb RAM. All run Ubuntu Server
12.04.
* Apache Server
o Apache
* App Server
o OFBiz / BigFish
o SOLR
* DB Server
o My SQL 5.6.13
Comfortably handles 4000 average visitors with a peak of about 100
concurrent users. We are expecting 12,000 for daily peak in a couple of
weeks time ... and it is sized to handle twice that number.
Gotta love OFBiz and the caching model, works like a charm!
Nick
On 1/20/2014 9:55 AM, Ted Byers wrote:
On Mon, Jan 20, 2014 at 9:37 AM, Nick Rosser<[email protected]>
wrote:
All,
I'm pleased to announce that the latest OFBiz / BigFish implementation
is
now live.
Check out www.ihatestevensinger.com.
Interesting....
The site is tuned to perform with average daily visitors in the ~4000
range
with an expectation of peak traffic at 10,000 visitors per day as we
get
closer to Valentine's Day. Sales are running about 10% higher than this
time last year!
For more information about BigFish check out
http://bigfish.solveda.com.
Nick
Can I ask, what kind of hardware, and what OS, and what connectivity,
was
used for this level of traffic?
Cheers
Ted
