Joseph Bajin napsal(a):
On Nov 13, 2007 12:13 PM, Iñaki Baz Castillo <ibc(a)in.ilimit.es
<mailto:ibc@in.ilimit.es>> wrote:
Hi, MySQL tables of OpenSer created by the script are "MyISAM". Is
there any
reason for that instead of using InnoDB?
As I know:
MyISAM:
- Is faster reading and writting (except writting various entries to
same
table since it blocks the entire table).
- No transactions or rollbacks.
- Small disc space requeriments.
InnoDB:
- Transactions, rollbacks, restrictions in foreing keys.
- Faster writting various entries in same table (entry lock instead
of table
lock).
- More disc space and RAM requeriments.
Yes, it can be obvious that for OpenSer the engine MyISAM can be a
good choice
but I would like to know if there is more data for this choice.
Regards.
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es <mailto:ibc@in.ilimit.es>
_______________________________________________
Users mailing list
Users(a)lists.openser.org <mailto:Users@lists.openser.org>
http://lists.openser.org/cgi-bin/mailman/listinfo/users
Depending on how much data you have, you should also look at mysql
Cluster. Since it is an in memory database, it will be super fast.
I have used SER with Mysql Cluster and it works well.
Joe
It is very interesting for me :-)
Could you tell me, please, how much users do you have and - it is what I
need to know - how much SELECTs and INSERTs per second your cluster can
serve and what type of SW (distribution, MySQL version) and HW (number
of nodes, type of CPUs per node) you are using?
I'm facing big challenge - need to maintain about 3.000-5.000 calls per
second with a lot of DB processing (say about 7 SELECT, 2 INSERTs and 3
UPDATEs per call).
Thanks a lot!
kokoska.rokoska
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users