Hi,
> One of the question being asked that I have no information is that how
> much disk space would it really needs?
That pretty much depends on what you are archiving: What kind of PV
(datatype)? What's the update rate (keep in mind that monitoring
death-bands can make it difficult to predict the average rate)? Adding
an index to your database to speed up data retrieval can roughly double
the amount of disk space you need. With MySQL you can use different
storage engines which will give you different storage efficiency.
So long story short: The easiest thing is to give it a try. Set
everything up on a PC or virtual machine and measure yourself. According
to my experience you do not need a high performance machine for a test.
If your disk is too slow, switch off regular flushing to disk. But keep
in mind that you can lose your data with a setup like this. See [1] for
some details you might want to consider for a production machine (most
of it should apply to MySQL as well).
If you're striving for high storage efficiency, you might even want to
look at transparent filesystem compression like it is included in ZFS.
Best regards,
Martin
[1] http://accelconf.web.cern.ch/AccelConf/pcapac2012/papers/wepd03.pdf
- Replies:
- Re: RDB archiver disk space Jiro Fujita
- Navigate by Date:
- Prev:
Re: Custom file saving plugin in AreaDetector Hinko Kočevar
- Next:
Re: RDB archiver disk space Jiro Fujita
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RDB archiver disk space Jiro Fujita
- Next:
Re: RDB archiver disk space Jiro Fujita
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
<2013>
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|