Thread: Fw: Google summer code idea
Hello, everybody!
Introduction at first.
I am a student, attempting at magister degree in "applied math" in Physical-Technical Institute of National Technical University of Ukraine “Kyiv Polytechnic Institute”. (don't be confused by double "institute", it a proper naming, although strange even for students).
When looking at the list of ideas suggested for google SoC I've found two of them that I'd like to be a part of.
First one - is fixing small memory leaks in ecpg, which is a certain variant, due to my experience with code digging, memory issues and memory profilers. It's quite a routine, but good practice task.
Second one is optional, due to it isn't marked as [E] task, but it strongly correlates with my knowledge.
It is implementing a faster CRC32 algorithm. I've read both discussion threads about it, and still consider myself probable of being involved in it.
My confidence in this fact is due to that fact that I am educated in algorithms estimation, codes, polynom operations and performance tests.
And here is the brief road-maps for this ideas.
The first task consists of:
* use profilers to identify automatically tracable leaks (1w)
* try to get rid of them (3w)
* try to find some complex leaks not found automatically (1w, just in case)
* test the changes (3w)
* cleanup and documentation (2w)
Second task, if acceptable, consists of mainly research and testing statistics for different variants and approaches.
There also can be a variant of early finishing idea with memory leaks cleanup, and contributing into the CRC task.
with regards,
Arsenii Bochechko
> First one - is fixing small memory leaks in ecpg, which is a certain > variant, due to my experience with code digging, memory issues and memory > profilers. It's quite a routine, but good practice task. Are you talking about ecpg itself or its libraries? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
About ecpg itself and its libraries. Though in this way it looks more like a full summer task than "just ecpg".
> First one - is fixing small memory leaks in ecpg, which is a certain > variant, due to my experience with code digging, memory issues and memory > profilers. It's quite a routine, but good practice task. Are you talking about ecpg itself or its libraries? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! For?a Bar?a! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- Sent via pgsql-students mailing list (pgsql-students@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-students
On Wed, Apr 24, 2013 at 03:11:52PM +0300, Бочечко Арсений wrote: > About ecpg itself and its libraries. Though in this way it looks more > like a full summer task than "just ecpg". I'm not aware of any leak in the libraries, but if there was one, a fix is really important. As far as "leaks" in ecpg go, I consider them very low priority because ecpg itself is just a very short running app and memory gets freed upon exit anyway. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
Ok. Then "leaks" are verified as a bad task, because there is no references of leaks in libraries.
--- Исходное сообщение ---
От кого: "Michael Meskes" <meskes@postgresql.org>
Дата: 24 апреля 2013, 16:53:12
От кого: "Michael Meskes" <meskes@postgresql.org>
Дата: 24 апреля 2013, 16:53:12
On Wed, Apr 24, 2013 at 03:11:52PM +0300, Бочечко Арсений wrote: > About ecpg itself and its libraries. Though in this way it looks more > like a full summer task than "just ecpg". I'm not aware of any leak in the libraries, but if there was one, a fix is really important. As far as "leaks" in ecpg go, I consider them very low priority because ecpg itself is just a very short running app and memory gets freed upon exit anyway. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at gmail dot com VfL Borussia! For?a Bar?a! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- Sent via pgsql-students mailing list (pgsql-students@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-students