pg.ddx.io  pgsql-students@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Fw: Google summer code idea
5+ messages / 2 participants
[nested] [flat]

* Fw: Google summer code idea
@ 2013-04-24 11:28 Бочечко Арсений <slua@ukr.net>
  2013-04-24 11:50 ` Re: Fw: Google summer code idea Michael Meskes <meskes@postgresql.org>
  0 siblings, 1 reply; 5+ messages in thread

From: Бочечко Арсений @ 2013-04-24 11:28 UTC (permalink / raw)
  To: pgsql-students




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

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Fw: Google summer code idea
  2013-04-24 11:28 Fw: Google summer code idea Бочечко Арсений <slua@ukr.net>
@ 2013-04-24 11:50 ` Michael Meskes <meskes@postgresql.org>
  2013-04-24 12:11   ` Re: Fw: Google summer code idea Бочечко Арсений <slua@ukr.net>
  0 siblings, 1 reply; 5+ messages in thread

From: Michael Meskes @ 2013-04-24 11:50 UTC (permalink / raw)
  To: Бочечко Арсений <slua@ukr.net>; +Cc: pgsql-students

> 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



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Fw: Google summer code idea
  2013-04-24 11:28 Fw: Google summer code idea Бочечко Арсений <slua@ukr.net>
  2013-04-24 11:50 ` Re: Fw: Google summer code idea Michael Meskes <meskes@postgresql.org>
@ 2013-04-24 12:11   ` Бочечко Арсений <slua@ukr.net>
  2013-04-24 13:52     ` Re: Fw: Google summer code idea Michael Meskes <meskes@postgresql.org>
  0 siblings, 1 reply; 5+ messages in thread

From: Бочечко Арсений @ 2013-04-24 12:11 UTC (permalink / raw)
  To: Michael Meskes <meskes@postgresql.org>; +Cc: pgsql-students




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  

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Fw: Google summer code idea
  2013-04-24 11:28 Fw: Google summer code idea Бочечко Арсений <slua@ukr.net>
  2013-04-24 11:50 ` Re: Fw: Google summer code idea Michael Meskes <meskes@postgresql.org>
  2013-04-24 12:11   ` Re: Fw: Google summer code idea Бочечко Арсений <slua@ukr.net>
@ 2013-04-24 13:52     ` Michael Meskes <meskes@postgresql.org>
  2013-04-24 14:20       ` Re: Fw: Google summer code idea Бочечко Арсений <slua@ukr.net>
  0 siblings, 1 reply; 5+ messages in thread

From: Michael Meskes @ 2013-04-24 13:52 UTC (permalink / raw)
  To: Бочечко Арсений <slua@ukr.net>; +Cc: Michael Meskes <meskes@postgresql.org>; 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


-- 
Sent via pgsql-students mailing list (pgsql-students@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-students



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Fw: Google summer code idea
  2013-04-24 11:28 Fw: Google summer code idea Бочечко Арсений <slua@ukr.net>
  2013-04-24 11:50 ` Re: Fw: Google summer code idea Michael Meskes <meskes@postgresql.org>
  2013-04-24 12:11   ` Re: Fw: Google summer code idea Бочечко Арсений <slua@ukr.net>
  2013-04-24 13:52     ` Re: Fw: Google summer code idea Michael Meskes <meskes@postgresql.org>
@ 2013-04-24 14:20       ` Бочечко Арсений <slua@ukr.net>
  0 siblings, 0 replies; 5+ messages in thread

From: Бочечко Арсений @ 2013-04-24 14:20 UTC (permalink / raw)
  To: Michael Meskes <meskes@postgresql.org>; +Cc: Michael Meskes <meskes@postgresql.org>; pgsql-students




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

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  

^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2013-04-24 14:20 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-04-24 11:28 Fw: Google summer code idea Бочечко Арсений <slua@ukr.net>
2013-04-24 11:50 ` Michael Meskes <meskes@postgresql.org>
2013-04-24 12:11   ` Бочечко Арсений <slua@ukr.net>
2013-04-24 13:52     ` Michael Meskes <meskes@postgresql.org>
2013-04-24 14:20       ` Бочечко Арсений <slua@ukr.net>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox