>> Third, you need to >> > setup your tables/indexes to use a < 100% fill-factor, this will allow >> > HOT updates to work. >> >> # ALTER TABLE dspam_token_data SET ( FILLFACTOR = 100 ); >> > You need to use a value for fillfactor that is less than 100%, otherwise any > update will be forced to use a new data page at the end of the table file > which will randomize your I/O over time.
Sorry!.. It should be OK now: # ALTER TABLE dspam_token_data SET ( FILLFACTOR = 90 ); >> Are you talking about "id_token_data_sumhits" index on the table? >> Should I drop it? OK. # DROP INDEX id_token_data_sumhits ; What about the PgSQLConnectionCache value? I set it 30.. By the way, I recognized that, While I am training dspam, total process time increases from 0.3-0.4 seconds to 5-10 seconds. !DSPAM:1011,489dbc83150921698418368!
