Thats why use it with _temporary data_ only, i use it for short term logs, some data involving geospatial computation -- I beats using flat file and grep at least. Anyway dont bring an axe to slice a tomato.
On 10/3/07, Orlando Andico <[EMAIL PROTECTED]> wrote: > > I actually benchmarked MySQL MEMORY table type. > > It's transactionless! (no commit/rollback) > > It's non-durable! (lose your data if MySQL or the server crashes) > > It's non-resilient! (MySQL Cluster replication is fragile and overly > complex) > > > But it's free. Oh well... > > > On 10/3/07, Roger Filomeno <[EMAIL PROTECTED]> wrote: > > Btw rather than using memcache, you can use MySQL MEMORY type tables but > be > > sure to use it for temporary data only since the data will be erased if > the > > server is restarted (and grab all the cheap RAM you can get). You can > use > > this with the federated tables feature to scale up. For PHP fans, u can > also > > use SHMOP. Linux purist, can also use the FIFO solution. > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > [email protected] (#PLUG @ irc.free.net.ph) > Read the Guidelines: http://linux.org.ph/lists > Searchable Archives: http://archives.free.net.ph > -- -- Roger P. Filomeno TechBiz Asia Group Pte Ltd http://corruptedpartition.blogspot.com/ send MSG GODIE <YOUR MESSAGE> to 2948 $> who | grep -i blond | date; cd ~; unzip; touch; strip; finger; mount; gasp; yes; uptime; umount; sleep
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
