mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Done:

Browse Source 
< * Improve SMP performance on i386 machines
> * -Improve SMP performance on i386 machines
This commit is contained in:
Bruce Momjian 2005-04-23 21:38:42 +00:00
parent 9b5b9616f4
commit bb62899db5
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/TODO
View File

@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Sat Apr 23 17:25:48 EDT 2005
Last updated: Sat Apr 23 17:38:41 EDT 2005
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -785,7 +785,7 @@ Locking
while on non-SMP machines, the backend should sleep so the process
holding the lock can complete and release it.
* Improve SMP performance on i386 machines
* -Improve SMP performance on i386 machines
i386-based SMP machines can generate excessive context switching
caused by lock failure in high concurrency situations. This may be

4
doc/src/FAQ/TODO.html
View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Sat Apr 23 17:25:48 EDT 2005
Last updated: Sat Apr 23 17:38:41 EDT 2005
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@ -718,7 +718,7 @@ first.
while on non-SMP machines, the backend should sleep so the process
holding the lock can complete and release it.
</p>
</li><li>Improve SMP performance on i386 machines
</li><li>-Improve SMP performance on i386 machines
<p> i386-based SMP machines can generate excessive context switching
caused by lock failure in high concurrency situations. This may be
caused by CPU cache line invalidation inefficiencies.