<html><body>><span style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; line-height: 16px;">It might be better to create a program to convert RRD files in one go</span><div><span style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; line-height: 16px;">> (we can already do an XML export/import of course) though this too </span></div><div><span style="color: rgb(0, 0, 0); font-family: Arial, sans-serif; line-height: 16px;">>could be more trouble than it is worth.</span></div><div><font color="#000000" face="Arial, sans-serif"><span style="line-height: 16px;"><br></span></font></div><div><font color="#000000" face="Arial, sans-serif"><span style="line-height: 16px;">I believe so, too. Reads/writes are done usually tens of thousands in</span></font></div><div><font color="#000000" face="Arial, sans-serif"><span style="line-height: 16px;">a monitoring period (with load peaks) while changing the architecture </span></font></div><div><font color="#000000" face="Arial, sans-serif"><span style="line-height: 16px;">of the machine </span></font><span style="line-height: 16px; color: rgb(0, 0, 0); font-family: Arial, sans-serif;">is done once a several years...</span></div><div><span style="line-height: 16px; color: rgb(0, 0, 0); font-family: Arial, sans-serif;"><br></span></div><div><span style="line-height: 16px; color: rgb(0, 0, 0); font-family: Arial, sans-serif;">In addition I believe that everyone who needed to export & import the </span></div><div><span style="line-height: 16px; color: rgb(0, 0, 0); font-family: Arial, sans-serif;">rrd </span><span style="line-height: 16px; color: rgb(0, 0, 0); font-family: Arial, sans-serif;">files has written such a tool himself.</span></div><div><span style="line-height: 16px; color: rgb(0, 0, 0); font-family: Arial, sans-serif;">;)</span> <span style="line-height: 16px; color: rgb(0, 0, 0); font-family: Arial, sans-serif;">jh</span></div><div><font color="#000000" face="Arial, sans-serif"><span style="line-height: 16px;"><br></span></font></div><div><br></div><div><p>---------- Původní zpráva ----------<br>Od: Steve Shipway <s.shipway@auckland.ac.nz><br>Datum: 21. 1. 2013<br>Předmět: Re: [rrd-users] Architecture independence for rrd files</p><br><blockquote>> I thought it would be a good idea on finding out how to make the rrd<br>> structure architecture independent, and if it's supposed to be, find<br>> out what's going on.<br><br>I believe Tobi is planning architecture-independence for the RRD file for RRDtool 2.x.<br><br>Making it arch-independent is not so easy (else it would have been done long ago as this has been on the cards some time). There are several problems relating to the generated C struct which is written to the file as created in memory:<br><br>1. endian - is it MSB first or LSB first (or middle byte first as in windows)<br>2. 23/64 bit - how big is an integer? This adjusts the size of the struct<br>3. alignment - does your architecture demand integers be byte-aligned and therefore generate padding bytes?<br>4. compiler peculiarities - some just do it differently at compile time.<br><br>The first is actively checked for by RRDTool (looking for different magic numbers in the header) and - I think - so is the second. Although it knows about them, though, working around it without losing a lot of efficiency would be a big problem.<br><br>It might be better to create a program to convert RRD files in one go (we can already do an XML export/import of course) though this too could be more trouble than it is worth.<br><br>I think there is more discussion on this in the Github area Tobi has set up https://github.com/oetiker/rrdtool-2.x<br><br>Steve<br><br>Steve Shipway<br>ITS Unix Services Design Lead<br>University of Auckland, New Zealand<br>Floor 1, 58 Symonds Street, Auckland<br>Phone: +64 (0)9 3737599 ext 86487<br>DDI: +64 (0)9 924 6487<br>Mobile: +64 (0)21 753 189<br>Email: s.shipway@auckland.ac.nz<br> Please consider the environment before printing this e-mail : 打印本邮件，将减少一棵树存活的机会</blockquote></div></body></html>