RE: Lower Level Visibility

[Sinisa Milivojevic]

wendorf, pat writes:
> I'm not entirely familiar with how the daemon stores these values for the
> entire database, but I'm guessing it's done in memory.  Is it not possible
> to allocate storage for these values in memory for each table that has been
> opened?(they'd be removed once the table is destroyed, and not stored at all
> for temporary tables I guess). Another possibility might be to store the
> values in memory until the table is no longer in an "open" state (I'm
> assuming you don't flush and close the tables on every operation) and flush
> them to disk in the table closing code (hopefully reducing the latency of
> updating each time they change).
> 
> I like the idea of having it saved on disk as it would allow for persistent
> values during outages, so long as the system as a whole doesn't take too
> much of a performance hit.
> 
> What exactly is feature sponsoring?
> 
> - Pat


We have users with hundreds of thousands of permanent tables. Temporary
tables are not a problem, they can be all in a single vector. Keeping
it all just in memory could be memory-expensive, but it could be done
that way too, if we give a calculation of how much memory per table
would be required

Feature sponsoring means that you would pay for this feature to be
developed. This is not a feature that is planned in any of the future
versions of MySQl, but if you pay for it 


-- 
Regards,
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, FullTime Developer
/_/  /_/\_, /___/\___\_\___/   Larnaca, Cyprus
   <___/   www.mysql.com

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

RE: Lower Level Visibility

[wendorf, pat]

I'm not entirely familiar with how the daemon stores these values for the
entire database, but I'm guessing it's done in memory.  Is it not possible
to allocate storage for these values in memory for each table that has been
opened?(they'd be removed once the table is destroyed, and not stored at all
for temporary tables I guess). Another possibility might be to store the
values in memory until the table is no longer in an "open" state (I'm
assuming you don't flush and close the tables on every operation) and flush
them to disk in the table closing code (hopefully reducing the latency of
updating each time they change).

I like the idea of having it saved on disk as it would allow for persistent
values during outages, so long as the system as a whole doesn't take too
much of a performance hit.

What exactly is feature sponsoring?

- Pat

-Original Message-
From: Sinisa Milivojevic [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 20, 2001 7:27 AM
To: wendorf, pat
Cc: '[EMAIL PROTECTED]'
Subject: Lower Level Visibility


wendorf, pat writes:
 > Is it possible to observe Handler_read_next and Handler_read_key on a per
 > table basis? If not, could this feature be added?
 > 
 > I'm not subscribed to this list, please cc all replies back to this email
 > address.  
 > 
 > - Pat Wendorf
 > 
 > 

Hi!

It could be possible to implement it, but it would be more costly, as
data would have to be saved on disk. 

Would you be willing to sponsor this feature ??


-- 
Regards,
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, FullTime Developer
/_/  /_/\_, /___/\___\_\___/   Larnaca, Cyprus
   <___/   www.mysql.com

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php