Ilya Kosmodemiansky
CEO at Data Egret
About
Ilya is a co-founder and CEO at Data Egret (former PostgreSQL-Consulting). His previous experience encompasses such commercial databases as Oracle and DB2. Currently, Ilya works primarily with PostgreSQL with a focus on its performance and effective use in production. He sees the mission of PostgreSQL in substituting the commercial databases in high-performance mission-critical applications.
Ilya Kosmodemiansky has presented the following presentations
presented by Ilya Kosmodemiansky
Input-output performance problems are on every day agenda for DBAs since the databases exist. Volume of data grows rapidly and you need to get your data fast from the disk and moreover - fast to the disk. For most databases there is a more or less easy to find checklist of recommended Linux settings to maximize IO throughput. In most cases that checklist is good enough. But it is always better ...
more Tue 28 2017 Trainingpresented by Ilya Kosmodemiansky
video
This talk is prepared as a bunch of slides, where each slide describes a really bad way people can screw up their PostgreSQL database and provides a weight - how frequently I saw that kind of problem. Right before the talk I will reshuffle the deck to draw twenty random slides and explain you why such practices are bad and how to avoid running into them.
Wed 29 2017 Operationspresented by Ilya Kosmodemiansky
Linux operating system has lots of tuning options which can change performance of your PostgreSQL installation drastically. People often say that an Oracle DBA is 90% a DBA and 10% a UNIX engineer, for a Postgres DBA this correspondence can optimistically be 50:50 or even lower on the DBA part. For PostgreSQL, obviously, most important are storage-related options like vm.dirty*, IO elevators or...
more Operationspresented by Ilya Kosmodemiansky
PostgreSQL like any other classical database interacts with disks heavily and has dozens of disk-related settings. In order to keep an instance up and running under even moderate workloads, an average DBA needs to dig through PostgreSQL documentation, operating system documentation, hardware vendor manuals, a few books, plenty of blog posts, [HACKERS] and [PERFORM] mail lists archive and finall...
more Admin