[ previous ] [ next ] [ threads ]
 
 From:  Paul Taylor <ptaylor at addressplus dot net>
 To:  "Jonathan De Graeve" <Jonathan dot DeGraeve at imelda dot be>
 Cc:  "Manuel Kasper" <mk at neon1 dot net>, <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] Memory resident data
 Date:  Mon, 14 Aug 2006 21:22:39 -0400
Jonathan,

	I believe that I used Serialization for the "Snapshot" feature of  
the state table.  It worked very well for my purpose, and was easy to  
implement.

Paul

On Aug 14, 2006, at 7:30 PM, Jonathan De Graeve wrote:

> I'm looking at a way to store the CP data (or ny other data if needed)
> in an other way instead of loading/writing it everytime with the  
> need of
> parsing it.
>
>
>
> I have different possibilities:
>
> Serialisation (keeps the data structures intact, still writes  
> everything
> to a file but hell, its MFS ;) ) I don't know if this is going to give
> us the needed performance boost with +100 CP users
>
> Memcached: A daemon being responsible to store data in memory by
> writing/reading it to/from the daemon (but I think this is going to be
> an overhead since serialisation seems to almost perform the same task)
>
> http://www.php.net/manual/en/ref.memcache.php
>
>
>
> APC: Caching extensions for PHP that as far as I can see don't need a
> continuous running tcp daemon (like memcached)
>
> http://phpbuilder.com/manual/en/ref.apc.php &
> http://pecl.php.net/package/apc
>
>
>
> I think both serialisation as APC sounds good but I'm not sure which
> ones to choose from.
>
>
>
> Any suggestions would been appreciated
>
>
>
> J.
>
>
>
> --
> Jonathan De Graeve
> Network/System Engineer
>
> Imelda vzw
> Informatica Dienst
> 015/50.52.98
> Jonathan dot de dot graeve at imelda dot be
>
>
>