- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Multi Domain Server - Performance
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Multi Domain Server - Performance
Dear community.
I found the solution sk109236 - "High CPU / process crashes / timeout due to large database / first time operations / load on the machine".
The solution to get better performance is to modify the connection buffer.
"The size of the Communication Buffer is hard-coded to 1MB-4MB depending on the version (For R77.10 and above: 4MB)."
"It is strongly suggested to set FWASYNC_MAXBUF=40000000 (or more, according to what the allocation failed on, i.e. if it failed on 40MB, then set to 80MB)"
- What does the buffer do?
- What is the limit of increasing the buffer?
- Why is 40 MB not default?
Regards
Roman
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Increasing a buffer (and yes, there are a lot of buffers in CP GWs and SMS !) adds to memory consumption, so when buffers are very large, swapping will occur and slow down the unit...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I believe FWASYNC_MAXBUF is used by the fwm process on a SMS to buffer incoming operations that fwm needs to perform. In R77.30 management and earlier, fwm had far too many responsibilities and was mostly single-threaded. This was a bad combination and led to fwm daemon crashes under heavy load which would eject the administrator from the SmartDashboard and all other GUI tools.
fwm still exists in R80+ management, but mainly to service the older legacy GUIs like the Smartview Monitor and SmartDashboard and a few other operations. Given the wholesale changes in R80+ management, fwm has much less to do these days and has been pretty stable from what I've seen; the new cpm daemon has taken over most of fwm's prior responsibilities. As such I wouldn't worry too much about increasing this buffer for fwm in R80+ management, unless you are actively seeing warnings about running out in $FWDIR/log/fwm.elg.
--
Second Edition of my "Max Power" Firewall Book
Now Available at http://www.maxpowerfirewalls.com
CET (Europe) Timezone Course Scheduled for July 1-2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for the answers.
We are using R77.30 Take 292.
$FWDIR/log/fwm.elg is not there.
I increased the buffer to 80 MB. It seems to work better, now.
Regards
Roman
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Next thing we did was to delete the caching file $FWDIR/conf/CPMILinksMgr.db
It was 60 Gb and maked more free RAM space.
128/125 Gb used to 128/70 Gb
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Roman,
we are using these parameters since more than 1 year on R77.30 with HFA T225 (and earlier). We configured it on the MDS and the GWs and the last time I read this SK the limit was about 64MB and this is what we configured.
To be honest I don't know what we want to solve in the past with this buffer. I did not notice any bad side effects.
Regards
