Index Pooling?

[reyortsed]

I cant see that there is any form of pooling for open indexes... This means that HandlerSocket is not great for pages which simply do single look-ups from several tables. In this case, its seems faster with standard mysql connection. Is there any plan to have such a feature so we may choose to keep persistent open index handles across requests?

Cheers

//Steve

[ahiguti]

You can use persistent connections to keep indexes open across multiple requests.

[reyortsed]

Could you show me some example code on how to do that? I do not see it documented or in example code... thanks

//Steve

[ahiguti]

# open a connection
my $hs = new Net::HandlerSocket($args);
# open indexes you need
$hs->open_index(1, 'db1', 'table1', 'index1', '...');
$hs->open_index(2, 'db2', 'table2', 'index2', '...');
$hs->open_index(3, 'db3', 'table3', 'index3', '...');
# execute requests
$hs->execute_single(...); # or execute_multi()
$hs->execute_single(...);
$hs->execute_single(...);
# don't dispose $hs. reuse $hs as far as possible and execute many requests on it.
$hs->execute_single(...);
...

If your app is a web based, you need to use a web app framework which supports object pooling (e.g., fastcgi) to keep $hs open across multiple http requests.

[reyortsed]

I have been using multiple executes on same index yes... it was keeping the index open across multiple http requests which I meant...