| From: | Evgeniy Shishkin <itparanoia(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: effective_io_concurrency's steampunk spindle maths |
| Date: | 2020-03-07 10:54:40 |
| Message-ID: | 66DAACA8-AFD1-4EC9-872C-CF7C750B0CEE@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Mar 7, 2020, at 00:33, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
>
> That is indeed what led me to start thinking about what a good new
> name would be.
MySQL has a term io_capacity.
https://dev.mysql.com/doc/refman/8.0/en/innodb-configuring-io-capacity.html
> The innodb_io_capacity variable defines the overall I/O capacity available to InnoDB. It should be set to approximately the number of I/O operations that the system can perform per second (IOPS). When innodb_io_capacity is set, InnoDB estimates the I/O bandwidth available for background tasks based on the set value.
>
Perhaps we can have maintenance_io_capacity as well.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Shaplov | 2020-03-07 12:14:42 | Re: [PATCH] Finally split StdRdOptions into HeapOptions and ToastOptions |
| Previous Message | Peter Eisentraut | 2020-03-07 10:05:54 | SQL/MDA added to docs |