[Tickets #7363] share sql driver performance

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Created By         | leena.heino@...
  Summary            | share sql driver performance
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | New
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


leena.heino@... (2008-09-19 13:12) wrote:

It seems that these bitwise operations in share sql-driver is a major  
performance killer at least in MySQL. This seems to be because SQL's  
bitwise operations do not use index in MySQL and therefore each query  
made in share sql-driver has to make a full table scan.

Would it be possible to change the database schema and the code so  
that each permission to different user type (creator/default/guest)  
would be stored in its own column and therefore we would have columns  
like perm_creator_show, perm_creator_read, perm_creator_edit and  
perm_creator_delete. This would allow us to ditch the bitwise  
operations in the query.

Instead of current query like this:
SELECT DISTINCT s.*  FROM nag_shares s
LEFT JOIN nag_shares_users AS u
ON u.share_id = s.share_id WHERE s.share_owner = 'foo'
OR (s.perm_creator & 4) != 0
OR (s.perm_default & 4) != 0
OR ( u.user_uid = 'foo' AND (u.perm & 4) != 0)
ORDER BY s.attribute_name ASC;

we could do the same query as:
SELECT DISTINCT s.*  FROM nag_shares s
LEFT JOIN nag_shares_users AS u
ON u.share_id = s.share_id WHERE s.share_owner = 'foo'
OR (s.perm_creator_read = 1)
OR (s.perm_default_read = 1)
OR ( u.user_uid = 'foo' AND (u.perm_read = 1))
ORDER BY s.attribute_name ASC;

Or maybe rewriting the query using subquery and union:
SELECT DISTINCT * FROM ((SELECT s.* FROM nag_shares s
WHERE (s.perm_creator = 1)
OR (s.perm_default = 1)
OR (s.share_owner = 'foo')) UNION (SELECT s.* FROM nag_shares s
LEFT JOIN kronolith_shares_users AS u ON u.share_id = s.share_id WHERE  
(u.user_uid = 'foo'
AND (u.perm = 1)))) AS new_s ORDER BY new_s.attribute_name ASC;

Perhaps gaining a better utilization of index in the database queries.




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Chuck Hagenbuch <chuck@...>
-Summary            | share sql driver performance
+Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
-State              | New
+State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck@...> (2008-09-20 13:55) wrote:

I still think this is worth exploring, but Jan and Michael R have  
raised some good points on how we can support custom permissions (such  
as Kronolith's PERMS_DELEGATE) in a BC way.




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | duck@...
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck@...> (2008-09-20 13:55) wrote:

I still think this is worth exploring, but Jan and Michael R have  
raised some good points on how we can support custom permissions (such  
as Kronolith's PERMS_DELEGATE) in a BC way.





--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | adrieder@...
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


adrieder@... (2008-09-21 04:50) wrote:

> Or maybe rewriting the query using subquery and union:
[....]
> Perhaps gaining a better utilization of index in the database queries.

In my tests (I think it should read "LEFT JOIN nag_shares_users"  
instead of "LEFT JOIN kronolith_shares_users") your modified query  
with the subquery was up to 6 times as fast as the original query. The  
database holds about 12,000 shares.





--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Chuck Hagenbuch <chuck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
+New Attachment     | explains.txt
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck@...> (2008-10-01 16:25) wrote:

Some EXPLAIN output for Share_sql vs. Share_datatree. Neither is  
great, and the datatree query isn't doing as much work, but the  
Share_sql query as is now is clearly pretty bad.





--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Chuck Hagenbuch <chuck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Duck <duck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Duck <duck@...> (2008-10-06 05:14) wrote:

Mysql does not uses indexes for bitwise operations. So it performs a  
full table scan. I was aware of this while I was writing the native  
driver. But I let this problem as it is still much better than the DT  
driver and had no time to solve even this. This part is still on my  
TODO...

Another table scan was introduced in in revision 1.35 of mrubinsk by  
adding the DISTINCT statement in the SQL query. And this is the *real*  
performance killer for MySQL. As it must scan the joined table - it  
means that must allocate a new temporary table with all joined data,  
using limit or not. Brrr....

So we must reorganize data  and query to avoid this two table scans.




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Michael Rubinsky <mrubinsk@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk@...> (2008-10-06 09:46) wrote:

The DISTINCT was/is necessary to avoid counting the same share more  
than once when the share has more than one entry in either the *_users  
or *_groups table. Otherwise, we get erroneous share counts.

Not ideal, but necessary with the current implementation. I agree  
things need to be reorganized after seeing the results of those  
EXPLAIN statements.




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Michael Rubinsky <mrubinsk@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk@...> (2008-10-06 10:03) wrote:

Actually, looking over the code now, it looks like we *might* be able  
to drop the duplicates (and get rid of the need for the DISTINCT  
qualifier) where we need to in PHP code. Not 100% sure yet, and it  
would probably require an extra loop in _countShares(), but it might  
be worth it if it's possible.




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Michael Rubinsky <mrubinsk@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
-Patch              |
+Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
+New Attachment     | sql.php.patch
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk@...> (2008-10-06 10:39) wrote:

What about something like this for removing the DISTINCT?

Ran it through a few common tasks in Turba, but not tested in depth.





--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Duck <duck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
+New Attachment     | sql.diff
------------------------------------------------------------------------------


Duck <duck@...> (2008-10-06 13:35) wrote:

In general I am counter to a solution on the PHP part. As you still  
need to load the data on the client site (probably from a remote  
server) and process it.

What about GROUP BY?
DISTINCT is normaly used to remove duplicates. GROUP BY to aggregate  
operators to each group. In our occasion DISTINCT and GROUP BY  
generates the same query plan. Probably will be faster to use GROUP BY  
for listings as better results in joins.
Even for counting we can use GROUP BY where we need to return just the  
number of rows affected instead of looping it into the countShares().

Look at the patch. And try it on your data.




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Chuck Hagenbuch <chuck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck@...> (2008-10-06 16:03) wrote:

Can either/both of you provide EXPLAIN output for these patches?





--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Michael Rubinsky <mrubinsk@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
+New Attachment     | mrubinsk_explains.txt
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk@...> (2008-10-06 18:16) wrote:

Very small dataset, so I'm not sure how helpful this is, but here it  
is.  For me, both GROUP BY and DISTINCT are using a temporary tables.





--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Duck <duck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Duck <duck@...> (2008-10-08 09:36) wrote:

> I still think this is worth exploring, but Jan and Michael R have
> raised some good points on how we can support custom permissions
> (such as Kronolith's PERMS_DELEGATE) in a BC way.

if PERMS_DELEGATE and other custom permissions must be possible, we  
can still do as with attributes - relay on table structure. We can  
detect fields on _save() and select with *.





--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Duck <duck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Duck <duck@...> (2008-10-08 11:38) wrote:

> For me, both GROUP BY and DISTINCT are using a temporary tables.

This is normal. As a temporary table is created for every join. Then  
depends on the data length and server settings if a table is created  
in memory or on disk.






--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Duck <duck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
+New Attachment     | shares.tgz
------------------------------------------------------------------------------


Duck <duck@...> (2008-10-08 11:54) wrote:

I create a new version of sql and sql_heirarical driver that stores  
every permission type in its own column. It checks table structure so  
even custom permission like PERM_DELEGATE from Kronolith should work  
if a columns like perm_default/guest/creater_delegate will be created.  
If share caching is enabled, it check the table structure only once  
per session.

I tested the driver with Spread and Ansel. So it should work but is  
not fully tested. I will try to make some performance test on my large  
installation (63k galleries).




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Duck <duck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Duck <duck@...> (2008-10-09 03:13) wrote:

ACTUAL QUERY  - time: 2.062
SELECT DISTINCT s.*  FROM ansel_shares s  LEFT JOIN ansel_shares_users  
AS u ON u.share_id = s.share_id WHERE ( (s.share_owner = 'duck' OR  
(s.perm_creator & 2) != 0 OR (s.perm_default & 2) != 0 OR ( u.user_uid  
= 'duck' AND (u.perm & 2) != 0))  AND attribute_images > 2) AND  
(s.share_parents = '' OR s.share_parents IS NULL) ORDER BY s.share_id  
DESC

FLAT CRITERIA - time: 2.031
SELECT DISTINCT s.*  FROM ansel_shares s  LEFT JOIN ansel_shares_users  
AS u ON u.share_id = s.share_id WHERE ( (s.share_owner = 'duck' OR  
(s.perm_creator_show = 1) OR (s.perm_default_show = 1) OR ( u.user_uid  
= 'duck' AND u.perm_show = 1))  AND attribute_images > 2) AND  
(s.share_parents = '' OR s.share_parents IS NULL) ORDER BY s.share_id  
DESC

WITHOUT PARENTELS IF NOT NEEDED  - time: 1.964
SELECT DISTINCT s.*  FROM ansel_shares s  LEFT JOIN ansel_shares_users  
AS u ON u.share_id = s.share_id WHERE ( (s.share_owner = 'duck' OR  
s.perm_creator_show = 1  OR s.perm_default_show = 1  OR ( u.user_uid =  
'duck' AND u.perm_show = 1 ))  AND attribute_images > 2) AND  
(s.share_parents = '' OR s.share_parents IS NULL) ORDER BY s.share_id  
DESC

JOIN CIRTERIA OUT OF WHERE  - time: 1.9208
SELECT DISTINCT s.*  FROM ansel_shares s  LEFT JOIN ansel_shares_users  
AS u ON u.share_id = s.share_id AND u.user_uid = 'duck' AND  
u.perm_show = 1 WHERE ( (s.share_owner = 'duck' OR s.perm_creator_show  
= 1  OR s.perm_default_show = 1) AND attribute_images > 2) AND  
(s.share_parents = '' OR s.share_parents IS NULL) ORDER BY s.share_id  
DESC





--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Chuck Hagenbuch <chuck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck@...> (2008-11-04 12:08) wrote:

Duck - as far as I know you have the largest data set for shares.  
Could you make it available for others to use in performance testing?  
Alternately, we could generate some random test data and use that. I  
know it'd be better than my local database for real scale testing.




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | Duck <duck@...>
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Duck <duck@...> (2008-11-05 06:11) wrote:

> Duck - as far as I know you have the largest data set for shares.
> Could you make it available for others to use in performance testing?
> Alternately, we could generate some random test data and use that. I
> know it'd be better than my local database for real scale testing.

I will prepare some testing data and some possible structures in the  
next days.




--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...

[bugs-14]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7363
------------------------------------------------------------------------------
  Ticket             | 7363
  Updated By         | crohmann@...
  Summary            | Avoid bitwise operations in the SQL Share driver
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Horde Developers, Chuck Hagenbuch
------------------------------------------------------------------------------


Duck <duck@...> (2008-11-05 06:11) wrote:

> Duck - as far as I know you have the largest data set for shares.
> Could you make it available for others to use in performance testing?
> Alternately, we could generate some random test data and use that. I
> know it'd be better than my local database for real scale testing.

I will prepare some testing data and some possible structures in the  
next days.





--
You are subscribed to this list as: lists@...
To unsubscribe, mail: bugs-unsubscribe@...