ubuntu linux system with multiple waveservers, memory usage grows with time.
16 views
Skip to first unread message
Stephen Brewer
unread,
May 7, 2013, 5:42:54 PM5/7/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to earthwo...@googlegroups.com
Has anyone found that on an ubuntu linux, running multiple waveservers, memory grows 3 to 4 times larger, within 15 - 20 min. This is 64bit ubuntu linux 12.04, using a raidz2 file system, 18 instances of the wave_serverV, 1200+ traces, all with 1GB tanks. So probably not the most common sort of setup. I am using the gui system monitor tool. Memory usages starts at around 2+GB and then grow to 7+GB within 15min or so.
Just wondering if anyone else has seen this sort of behavior. This doesn't seem to happen on windows systems.
thanks, steve.
Stefan Lisowski
unread,
May 7, 2013, 6:12:01 PM5/7/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to earthwo...@googlegroups.com
Will 'top' or your GUI tool tell you what's eating the memory? Is
wave_serverV processes? Or some other system processes?
(Haven't see this behavior, but even with many traces coming in I've not
used so many wsV instances.)
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to earthwo...@googlegroups.com
No I have not looked into that carefully. Pretty sure that it is the
waveserverV processes though since that is the only thing different on
the system. It would be easy enough to try consolidating the traces into
fewer waveserverV instances. I'll try that.
It could possibly be the raidz file system. I have read some things
concerning zfs need for memory. I did think of trying the "standard" EFS
file system. I was most interested if whether anyone else had seen this
sort of behavior.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to earthwo...@googlegroups.com
Steven,
ZFS indeed uses memory for caching. The parameters are tunable tho. You
may want to limit how much memory ZFS can use. I personally do not use
ZFS on wavetanks.
Bill
========================================
Bill Blycker
Seismic Network Administrator
University of Utah Seismograph Stations
115 South 1460 East, Room 107 FASB
Salt Lake City, Utah 84112-0102
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to earthwo...@googlegroups.com
After looking into this, my conclusion is that you probably SHOULD NOT USE ZFS on your ubuntu, or any other linux system. I would refer people to both the ZFS on Linux FAQ (http://zfsonlinux.org/faq.html) and the ZFS on Linux Roadmap (https://github.com/zfsonlinux/zfs/issues/milestones). The native ZFS used by ubuntu is at version 0.6.1 If you look at some of the unresolved issues for even the upcoming 0.6.2 release, I think you can see why it is probably good not to use ZFS. Hope this helps someone avoid some inconvenience.