Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 2f2b58d

Browse files
committed
Spit items:
* Experiment with multi-threaded backend better I/O utilization This would allow a single query to make use of multiple I/O channels simultaneously. One idea is to create a background reader that can pre-fetch sequential and index scan pages needed by other backends. This could be expanded to allow concurrent reads from multiple devices in a partitioned table. * Experiment with multi-threaded backend better CPU utilization This would allow several CPUs to be used for a single query, such as for sorting or query execution.
1 parent 8426b56 commit 2f2b58d

File tree

2 files changed

+23
-14
lines changed

2 files changed

+23
-14
lines changed

doc/TODO

+12-7
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
PostgreSQL TODO List
22
====================
33
Current maintainer: Bruce Momjian (bruce@momjian.us)
4-
Last updated: Tue Mar 18 19:32:48 EDT 2008
4+
Last updated: Tue Mar 18 19:35:12 EDT 2008
55

66
The most recent version of this document can be viewed at
77
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1630,13 +1630,18 @@ Miscellaneous Performance
16301630

16311631
http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php
16321632

1633-
* Experiment with multi-threaded backend better resource utilization
1633+
* Experiment with multi-threaded backend better I/O utilization
16341634

1635-
This would allow a single query to make use of multiple CPU's or
1636-
multiple I/O channels simultaneously. One idea is to create a
1637-
background reader that can pre-fetch sequential and index scan
1638-
pages needed by other backends. This could be expanded to allow
1639-
concurrent reads from multiple devices in a partitioned table.
1635+
This would allow a single query to make use of multiple I/O channels
1636+
simultaneously. One idea is to create a background reader that can
1637+
pre-fetch sequential and index scan pages needed by other backends.
1638+
This could be expanded to allow concurrent reads from multiple devices
1639+
in a partitioned table.
1640+
1641+
* Experiment with multi-threaded backend better CPU utilization
1642+
1643+
This would allow several CPUs to be used for a single query, such as
1644+
for sorting or query execution.
16401645

16411646
* Consider increasing the minimum allowed number of shared buffers
16421647

doc/src/FAQ/TODO.html

+11-7
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
99
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
1010
<p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11-
Last updated: Tue Mar 18 19:32:48 EDT 2008
11+
Last updated: Tue Mar 18 19:35:12 EDT 2008
1212
</p>
1313
<p>The most recent version of this document can be viewed at<br/>
1414
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@@ -1415,12 +1415,16 @@ <h1><a name="section_21">Miscellaneous Performance</a></h1>
14151415
</p>
14161416
<p> <a href="http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php">http://archives.postgresql.org/pgsql-general/2007-02/msg00493.php</a>
14171417
</p>
1418-
</li><li>Experiment with multi-threaded backend better resource utilization
1419-
<p> This would allow a single query to make use of multiple CPU's or
1420-
multiple I/O channels simultaneously. One idea is to create a
1421-
background reader that can pre-fetch sequential and index scan
1422-
pages needed by other backends. This could be expanded to allow
1423-
concurrent reads from multiple devices in a partitioned table.
1418+
</li><li>Experiment with multi-threaded backend better I/O utilization
1419+
<p> This would allow a single query to make use of multiple I/O channels
1420+
simultaneously. One idea is to create a background reader that can
1421+
pre-fetch sequential and index scan pages needed by other backends.
1422+
This could be expanded to allow concurrent reads from multiple devices
1423+
in a partitioned table.
1424+
</p>
1425+
</li><li>Experiment with multi-threaded backend better CPU utilization
1426+
<p> This would allow several CPUs to be used for a single query, such as
1427+
for sorting or query execution.
14241428
</p>
14251429
</li><li>Consider increasing the minimum allowed number of shared buffers
14261430
<p> <a href="http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php">http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php</a>

0 commit comments

Comments
 (0)