Em 20/03/13, Filho Arrais<kuruminbra...@gmail.com> escreveu:
>
> Jean Domingues, não seria a aplicação cliente que dividira entre os
> núcleos, mas sim o próprio PostgreSQL.
>
> Veja só a imagem do link abaixo em raro momento de baixo processamento,
> pequei uma Thread que ta consumindo muito, utilizando somente um núcleo.
>
> http://i.imgur.com/rPlCaaT.jpg
>
Da TODO list [1]:
"
Features We Do Not Want
...
All backends running as threads in a single process (not wanted)
This eliminates the process protection we get from the current
setup. Thread creation is usually the same overhead as process
creation on modern systems, so it seems unwise to use a pure threaded
model, and MySQL and DB2 have demonstrated that threads introduce as
many issues as they solve. Threading specific operations such as I/O,
seq scans, and connection management has been discussed and will
probably be implemented to enable specific performance features.
Moving to a threaded engine would also require halting all other work
on PostgreSQL for one to two years.
"
Osvaldo
[1] http://wiki.postgresql.org/wiki/Todo
_______________________________________________
pgbr-geral mailing list
pgbr-geral@listas.postgresql.org.br
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
