Обсуждение: GSoC Proposal - Caching query results in pgpool-II

Поиск
Список
Период
Сортировка

GSoC Proposal - Caching query results in pgpool-II

От
Masanori Yamazaki
Дата:
Hello<br /><br /> I am sending my proposal about Google Summer Of Code2011. <br />It would be nice if you could give me
youropinion.<br /><br />・title<br /><br />Caching query results in pgpool-II<br /><br /><br />・Synopsis<br /><br
/>Pgpool-IIhas query caching functionality using storage provided by<br /> dedicated PostgreSQL ("system database").
Thishas several drawbacks<br />however. 1)it is slow because it needs to access disk storage 2)it<br />does not
invalidatethe cache automatically.<br /><br />This proposal tries to solve these problems.<br /><br />- To speed up the
cacheaccess, it will be placed on memory, rather<br />  than database. The memory will be put on shared memory or
external<br/>  memory services such as memcached so that the cache can be shared by<br />   multiple sessions. Old
cacheentries will be deleted by LRU manner.<br /><br />- The cache will be invalidated automatically upon the timing
whenthe<br />  relevant tables are updated. Note that this is not always possible<br />   because the query result
mightcome from multiple tables, views or<br />  even functions. In this case the cache will be invalidated by<br /> 
timeout(orthey are not cached at all).<br /><br />- Fine tuning knobs need to be invented to control the cache
behavior<br/>   though they are not clear at this moment.<br /><br /><br />・Benefits to the PostgreSQL Community:<br
/><br/><br />Query caching will effectively enhance the performance of PostgreSQL<br />and this project will contribute
toincrease the number of users of<br /> PostgreSQL, who need more high performance database systems.<br /><br />Note
thatimplementing query cache in pgpool-II will bring merits not<br />only to the latest version of PostgreSQL but to
theprevious releases<br />of PostgreSQL.<br /><br /><br />・Project Schedule<br /><br />-April<br /> preparation <br
/><br/>-May 1 - May 22 <br /> write a specification<br /><br />-May 23 - June 19<br /> coding<br /><br />-June 20 -
July22<br /> test<br /><br />-July 23 - August 12<br /> Complete of coding and test, commit<br /><br /><br />・Personal
Dataand Biographical Information<br /><br /> Name : Masanori Yamazaki<br /> Born : 23.1.1981<br /> School :Currently I
learncontemporary philosophy, culture and literature at Waseda University in Japan.<br /> Coding :<br />  1.About five
yearsjob as web application programer(PHP, Java).<br /> 2.I experienced projects used framework such as Symfony, Zend
Framework,CakePHP, and Struts.<br /> 3.I am interested in OSS and like coding.<br /><br /><br />Regards<br /><br /><br
/>

Re: GSoC Proposal - Caching query results in pgpool-II

От
Tatsuo Ishii
Дата:
I like this proposal. This would bring big benefit to both the
PostgreSQL and the pgpool project.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> Hello
> 
>  I am sending my proposal about Google Summer Of Code2011.
> It would be nice if you could give me your opinion.
> 
> ・title
> 
> Caching query results in pgpool-II
> 
> 
> ・Synopsis
> 
> Pgpool-II has query caching functionality using storage provided by
> dedicated PostgreSQL ("system database"). This has several drawbacks
> however. 1)it is slow because it needs to access disk storage 2)it
> does not invalidate the cache automatically.
> 
> This proposal tries to solve these problems.
> 
> - To speed up the cache access, it will be placed on memory, rather
>   than database. The memory will be put on shared memory or external
>   memory services such as memcached so that the cache can be shared by
>   multiple sessions. Old cache entries will be deleted by LRU manner.
> 
> - The cache will be invalidated automatically upon the timing when the
>   relevant tables are updated. Note that this is not always possible
>   because the query result might come from multiple tables, views or
>   even functions. In this case the cache will be invalidated by
>   timeout(or they are not cached at all).
> 
> - Fine tuning knobs need to be invented to control the cache behavior
>   though they are not clear at this moment.
> 
> 
> ・Benefits to the PostgreSQL Community:
> 
> 
> Query caching will effectively enhance the performance of PostgreSQL
> and this project will contribute to increase the number of users of
> PostgreSQL, who need more high performance database systems.
> 
> Note that implementing query cache in pgpool-II will bring merits not
> only to the latest version of PostgreSQL but to the previous releases
> of PostgreSQL.
> 
> 
> ・Project Schedule
> 
> -April
>  preparation
> 
> -May 1 - May 22
>  write a specification
> 
> -May 23 - June 19
>  coding
> 
> -June 20 - July 22
>  test
> 
> -July 23 - August 12
>  Complete of coding and test, commit
> 
> 
> ・Personal Data and Biographical Information
> 
>  Name : Masanori Yamazaki
>  Born : 23.1.1981
>  School :Currently I learn contemporary philosophy, culture and literature
> at Waseda University in Japan.
>  Coding :
>  1.About five years job as web application programer(PHP, Java).
>  2.I experienced projects used framework such as Symfony, Zend Framework,
> CakePHP, and Struts.
>  3.I am interested in OSS and like coding.
> 
> 
> Regards


Re: GSoC Proposal - Caching query results in pgpool-II

От
Selena Deckelmann
Дата:
2011/4/5 Masanori Yamazaki <myamazaki23@gmail.com>:
> Hello
>
>  I am sending my proposal about Google Summer Of Code2011.
> It would be nice if you could give me your opinion.

Fantastic!  Please submit your proposal through the GSoC website:

http://www.google-melange.com/gsoc/profile/student/google/gsoc2011

-selena



--
http://chesnok.com