Re: GSoC Proposal - Caching query results in pgpool-II - Mailing list pgsql-hackers
From | Magnus Hagander |
---|---|
Subject | Re: GSoC Proposal - Caching query results in pgpool-II |
Date | |
Msg-id | BANLkTi=_onbVNxEKX-sc3oxoqhOdUGLmMg@mail.gmail.com Whole thread Raw |
In response to | GSoC Proposal - Caching query results in pgpool-II (Masanori Yamazaki <m.yamazaki23@gmail.com>) |
Responses |
Re: GSoC Proposal - Caching query results in pgpool-II
|
List | pgsql-hackers |
<p>How does this relate to the existing pqc project ( <a href="http://code.google.com/p/pqc/">http://code.google.com/p/pqc/</a>)?Seems the goals are fairly similar, and both arebased off pgpool?<p>/Magnus<br /><div class="gmail_quote">On Apr 6, 2011 2:10 AM, "Masanori Yamazaki" <<a href="mailto:m.yamazaki23@gmail.com">m.yamazaki23@gmail.com</a>>wrote:<br type="attribution" />> Hello<br />> <br/>> My name is Masanori Yamazaki. I am sending my proposal about<br /> > Google Summer Of Code2011. It would benice if you could give<br />> me your opinion.<br />> <br />> <br />> ・title<br />> <br />> Caching queryresults in pgpool-II<br />> <br />> <br />> ・Synopsis<br />> <br /> > Pgpool-II has query caching functionalityusing storage provided by<br />> dedicated PostgreSQL ("system database"). This has several drawbacks<br/>> however. 1)it is slow because it needs to access disk storage 2)it<br /> > does not invalidate thecache automatically.<br />> <br />> This proposal tries to solve these problems.<br />> <br />> - To speedup the cache access, it will be placed on memory, rather<br />> than database. The memory will be put on shared memoryor external<br /> > memory services such as memcached so that the cache can be shared by<br />> multiple sessions.Old cache entries will be deleted by LRU manner.<br />> <br />> - The cache will be invalidated automaticallyupon the timing when the<br /> > relevant tables are updated. Note that this is not always possible<br />>because the query result might come from multiple tables, views or<br />> even functions. In this case the cachewill be invalidated by<br /> > timeout(or they are not cached at all).<br />> <br />> - Fine tuning knobs needto 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 enhancethe performance of PostgreSQL<br />> and this project will contribute to increase the number of users of<br />>PostgreSQL, who need more high performance database systems.<br /> > <br />> Note that implementing query cachein pgpool-II will bring merits not<br />> only to the latest version of PostgreSQL but to the previous 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 - June19<br />> coding<br />> <br />> -June 20 - July 22<br />> test<br />> <br />> -July 23 - August 12<br/> > complete of coding and test, commit<br />> <br />> <br />> ・Personal Data and Biographical Information<br/>> <br />> Name : Masanori Yamazaki<br />> Born : 23.1.1981<br />> School :Currently I learn contemporaryphilosophy, culture and literature<br /> > at Waseda University in Japan.<br />> Coding :<br />> 1.Aboutfive years job as web application programer(PHP, Java).<br />> 2.I experienced projects used framework such asSymfony, Zend Framework,<br />> CakePHP, and Struts.<br /> > 3.I am interested in OSS and like coding.<br />><br />> <br />> Regards<br /></div>
pgsql-hackers by date: