Yes. I've been running with store-by-group for over a year now. Not sure if its 
helping or not. Will assume that it is.

The main flaw that I see with JRobin & store-by-group is that's a compounded 
problem. Its not something you see when you look at it up close, you need to 
step back and look at it from whats happening at the OS level. The JRobin file 
format spreads its definition format all throughout the file. Each time you 
open the file, JRobin has to scan through it all so it "knows" where to 
read/write any updates. If you're application is continually opening and 
closing the files then you'll be ok as long as the total jrobin dataset is able 
to be cached by the OS's file buffercache. If you got beyond that limit, then 
the OS will have to continually read the blocks of the JRobin files into memory 
upon each open().

So with a large enough number of nodes+data collection points, OpenNMS+JRobin 
degenerates down to a pure random read/writes at the block level of your 
storage system leaving us with the worst case performance scenario.

My system has no problems doing the actual polling & datacollection. Its just 
that OpenNMS+JRobin causes it to not be able to write the data collected out to 
disk without having a large operations pending. Hence, whenever I restarted 
OpenNMS, my graphs all end up with a 30-60 minute block of no data to display.

Ron

-----Original Message-----
From: Tarus Balog [mailto:ta...@opennms.org] 
Sent: Monday, May 30, 2011 12:50 PM
To: OpenNMS Code Development and Bugs
Subject: Re: [opennms-devel] jrobin file format


On May 24, 2011, at 10:44 AM, Roskens, Ronald wrote:

> Well this is interesting. JRobin only caches cacheable values when you 
> set them, and never when they are read. Since OpenNMS is continually 
> opening and closing the jrb files, this could help somewhat as JRobin 
> is reading values from around the file while its updating them

Have you looked at the store-by-group option?

-T

_______________________________________________________________________
Tarus Balog, OpenNMS Maintainer             Main:   +1 919 533 0160
The OpenNMS Group, Inc.                     Fax:    +1 773 345 3645
Email: ta...@opennms.org                    URL: http://www.opennms.org
PGP Key Fingerprint: 8945 8521 9771 FEC9 5481  512B FECA 11D2 FD82 B45C



------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, you get 
blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this 
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel

This e-mail message is being sent solely for use by the intended recipient(s) 
and may contain confidential information.  Any unauthorized review, use, 
disclosure or distribution is prohibited.  If you are not the intended 
recipient, please contact the sender by phone or reply by e-mail, delete the 
original message and destroy all copies. Thank you.

------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list

To *unsubscribe* or change your subscription options, see the bottom of this 
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel

Reply via email to