NoteCaddy notes creation slow

[elcarlitro]

hi
I have a problem with creating notes.
After creating a new database with 2 million hands, the program is creating notes to 2h / s when at other times were more than 100 h/ s .
Previously I happened the same and was a corrupt note that I found it looking , the time needed deficiccion , create a note, but this option I do not remember , and I can not do it again
2 hour for processing 2000 hands
In datbase settings ,
What is a good setup for when I create a new database ? and notes to create more fast .


And to play alone ?

I have an i5 3470
8gb ddr3
ssd 500 gb

i have
thread count 4
use turbo hand grabber

use last X oporttunitis for notes 0
hm2 stast time out 10000
persit note to database 10000
i reset the computer and dont changes

thx

[sreticentv]

I'm not sure if you have seen this NoteCaddy speed improvement - Assaultware Wiki
With 2 million hands it's substantial database. Some efforts must be made by user even on lower database level.
Also very important is frequent database vacuum http://hm2faq.holdemmanager.com/ques...lyze+Database+

[elcarlitro]

hi
I had already done a vacum + analyce my database.
I have the same settings in notecady as in the photo " Setting NoteCaddy to use more system resources"
4 or 5 months to make notes of 2,000,000 hands need 4 hours
yesterday 2000 hands 2 hours.
It is a problem of any definition , it takes a long time to create a note , because something is wrong.
On another occasion the same thing happened . I put on the right of definition name , a column that wrote the time needed to create a note definition, totalruntime.

It was normal between 2 to -200 , one definition need 9999999 I delete it and again and everything worked well


I want to make Identifying slow definitions

IF I press right button on definition name , show column chooser , not the totalruntime now

How do I can see totalrun time again?

thank you very much

[sreticentv]

There is no more runtime column. You can look at the "total instances" and figure that any very large value will cause substantial slowing. Also make sure you're using postgres 9.0 since the earlier version may have some problem and 9.0 is better.