|
From: <And...@Be...> - 2001-12-06 08:52:21
|
Hey, y`all, so far, innodb tables seem to work right. Catch: no fulltext index at = the moment. I did not get around to testing gemini. I`ll keep this list up = to date. later, Andreas -----Urspr=FCngliche Nachricht----- Von: Chris Winters [mailto:ch...@cw...] Gesendet am: Montag, 3. Dezember 2001 04:24 An: Nolte, Andreas, D22K-MSN Cc: ope...@li... Betreff: Re: [Openinteract-help] OI with GEMINI * Andreas Nolte (And...@Be...) [011201 16:34]: > has anyone of you used OI with mysql and the GEMINI table type? We > have some concurrency problems, since we have a lot of updates and > inserts with auto_increment columns. The docs of mysql say, that > MyISAM talbes ( the default ) lock the whole table, before an > auto_increment insert can be made - this hurts performance badly in > our environment, where multiple users do updates / inserts at the > same time. I'd never heard this before, that it locks the whole table. Sheesh. Another alternative is dumping auto-incrementing fields entirely and using something else -- it probably wouldn't be too difficult to create a socket server (in Perl even!) to generate unique IDs. But this might have bigger problems that using the Gemini/InnoDB tables -- another point of failure, etc. Good luck Chris --=20 Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
|
From: <And...@Be...> - 2001-12-06 12:58:12
|
.. hard to tell on a test site - it seems, it does. But we shall see = on the production site... BTW: recently I posted our idea of using sys_security with = skip_security as a join to boost performance: this works great and speeds things up = noticebly with our critical requests, that is those, where the actual request = returns a lot of records, of which most are kicked out by the security = mechanism ( with one fetch for each record ! ). later, Andreas -----Urspr=FCngliche Nachricht----- Von: Chris Winters [mailto:ch...@cw...] Gesendet am: Donnerstag, 6. Dezember 2001 14:11 An: Nolte, Andreas, D22K-MSN Cc: ope...@li... Betreff: Re: [Openinteract-help] OI with GEMINI * Andreas Nolte (And...@Be...) [011206 04:01]: > so far, innodb tables seem to work right. Catch: no fulltext index at = the > moment. I did not get around to testing gemini. I`ll keep this list = up to > date. Good news! How has this affected the performance issues? Chris --=20 Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. _______________________________________________ openinteract-help mailing list ope...@li... https://lists.sourceforge.net/lists/listinfo/openinteract-help |
|
From: Chris W. <ch...@cw...> - 2001-12-08 15:05:38
|
* Andreas Nolte (And...@Be...) [011206 08:07]: > .. hard to tell on a test site - it seems, it does. But we shall see > on the production site... What?! You mean you didn't just run it on your production site? :-) > BTW: recently I posted our idea of using sys_security with > skip_security as a join to boost performance: this works great and > speeds things up noticebly with our critical requests, that is > those, where the actual request returns a lot of records, of which > most are kicked out by the security mechanism ( with one fetch for > each record ! ). Nice -- I'll have to look at incorporating this in the future. Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
|
From: <And...@Be...> - 2001-12-13 08:41:13
|
Hey, as promised, I`d like to comment on using other mysql table handlers = with OI: GEMINI: - I did NOT get a running site converted to GEMINI ! - I suspect, that it has to do with auto_increment columns - I did not test a fresh site with GEMINI - the legal status of GEMINI to me is quite unclear - MySQL AB and Nusphere seem to be at war, which leads me to rule this option out anyway InnoDB: - so far no problems at all! - only drawback: no fulltext indexes at the moment - concurrency issues sure have improved - conversion of tables from MYISAM to INNODB back and forth works = without any problems ( tested with sys_security and >200.000 records ) later, Andreas -----Urspr=FCngliche Nachricht----- Von: Chris Winters [mailto:ch...@cw...] Gesendet: Samstag, 8. Dezember 2001 16:27 An: And...@Be... Cc: ope...@li... Betreff: Re: [Openinteract-help] OI with GEMINI * Andreas Nolte (And...@Be...) [011206 08:07]: > .. hard to tell on a test site - it seems, it does. But we shall see > on the production site... What?! You mean you didn't just run it on your production site? :-) > BTW: recently I posted our idea of using sys_security with > skip_security as a join to boost performance: this works great and > speeds things up noticebly with our critical requests, that is > those, where the actual request returns a lot of records, of which > most are kicked out by the security mechanism ( with one fetch for > each record ! ). Nice -- I'll have to look at incorporating this in the future. Chris --=20 Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. _______________________________________________ openinteract-help mailing list ope...@li... https://lists.sourceforge.net/lists/listinfo/openinteract-help |
|
From: Chris W. <ch...@cw...> - 2001-12-13 12:58:28
|
* Andreas Nolte (And...@Be...) [011213 03:50]: > Hey, > > as promised, I`d like to comment on using other mysql table handlers > with OI: > ... > InnoDB: > - so far no problems at all! > - only drawback: no fulltext indexes at the moment > - concurrency issues sure have improved This is good news. Are you still using the sys_security JOIN method you mentioned before? BTW, I'm curious: how many people are using the site overall and at a single time? > - conversion of tables from MYISAM to INNODB back and forth works > without any problems (tested with sys_security and >200.000 records) Great -- painless conversions are always good. Thanks for writing this up. Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
|
From: <And...@Be...> - 2001-12-13 16:30:35
|
up to 800 Users will be using the site. Currently there are maybe 400, = about 50 of which use our NATS ticket system, which is the app where we use sys_security with JOINs for statistical overview lists, because we have about 15 clients in this system ( each department is a separat client = for us ) and sort the db entries out through security. For these lists we now = only have around 1/5 of the running time compared to the normal security mechanism. But as I wrote earlier: this is one specific usage where we wanted to do without the usual client_id row in each table.. Back to the users: the others are using simple table editor style apps = or just read manuals or else.=20 But this is only our intranet... Next we will do a we based order = system including credit card charges and SAP based product shippment for one = of our external clients ( german mobile phone company ), an extranet for our service center customers, so they can e.g. view their callcenter = reports online, replace access / vb frontend to our CRM systems, etc.. later, Andreas -----Urspr=FCngliche Nachricht----- Von: Chris Winters [mailto:ch...@cw...] Gesendet: Donnerstag, 13. Dezember 2001 14:20 An: And...@Be... Cc: ope...@li... Betreff: Re: [Openinteract-help] OI with GEMINI * Andreas Nolte (And...@Be...) [011213 03:50]: > Hey, >=20 > as promised, I`d like to comment on using other mysql table handlers > with OI: > ... > InnoDB: > - so far no problems at all! > - only drawback: no fulltext indexes at the moment > - concurrency issues sure have improved This is good news. Are you still using the sys_security JOIN method you mentioned before? BTW, I'm curious: how many people are using the site overall and at a single time? > - conversion of tables from MYISAM to INNODB back and forth works > without any problems (tested with sys_security and >200.000 records) Great -- painless conversions are always good. Thanks for writing this up. Chris --=20 Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |
|
From: Chris W. <ch...@cw...> - 2001-12-06 12:50:14
|
* Andreas Nolte (And...@Be...) [011206 04:01]: > so far, innodb tables seem to work right. Catch: no fulltext index at the > moment. I did not get around to testing gemini. I`ll keep this list up to > date. Good news! How has this affected the performance issues? Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |