[ 
https://issues.apache.org/jira/browse/DERBY-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kristian Waagan updated DERBY-4771:
-----------------------------------

    Attachment: derby-4771-2f-prototype_lcc_code_dump.diff

Attaching patch 2f, which contains mostly test improvements. I also fixed the 
bug in the property handling.

I'm not quite sure about the value of the multi-test, but the logging output 
shows that the code dealing with duplicates is stressed a bit:
$ grep istat system/derby.log 
Thu Dec 02 21:02:08 CET 2010 Thread[Thread-3,5,main] {istat} "APP"."MTSEL": 
update scheduled - 6c44409f-012c-a8ad-5f23-ffffb00d8f4e reason=[no stats, 
row-estimate=-80075] (queueSize=1)
Thu Dec 02 21:02:08 CET 2010 Thread[index-stat-thread,5,main] {istat} 
"APP"."MTSEL": generating index statistics
Thu Dec 02 21:02:08 CET 2010 Thread[index-stat-thread,5,main] {istat} 
"APP"."MTSEL": wrote stats for index ace4c0a3-012c-a8ad-5f23-ffffb00d8f4e 
(rows=100000, card=[10,100000]), 0.0% utilization
Thu Dec 02 21:02:08 CET 2010 Thread[index-stat-thread,5,main] {istat} 
"APP"."MTSEL": scan durations (c1153=124ms)
Thu Dec 02 21:02:08 CET 2010 Thread[index-stat-thread,5,main] {istat} 
"APP"."MTSEL": generation complete (269 ms)
Thu Dec 02 21:02:18 CET 2010 Thread[TestRunner-Thread,5,main] {istat} stopping 
daemon, active=false [q/p/s=0/1/1,err:k/u=0/0,rej=76]
Thu Dec 02 21:02:22 CET 2010 Thread[Thread-12,5,main] {istat} "APP"."MTSEL": 
update scheduled - b4df26ce-012c-a8ad-5f23-ffffb00d8f4e reason=[no stats, 
row-estimate=-80095] (queueSize=1)
Thu Dec 02 21:02:22 CET 2010 Thread[index-stat-thread,5,main] {istat} 
"APP"."MTSEL": generating index statistics
Thu Dec 02 21:02:22 CET 2010 Thread[index-stat-thread,5,main] {istat} 
"APP"."MTSEL": wrote stats for index 7baea6d2-012c-a8ad-5f23-ffffb00d8f4e 
(rows=100000, card=[10,100000]), 0.0% utilization
Thu Dec 02 21:02:22 CET 2010 Thread[index-stat-thread,5,main] {istat} 
"APP"."MTSEL": scan durations (c1185=72ms)
Thu Dec 02 21:02:22 CET 2010 Thread[index-stat-thread,5,main] {istat} 
"APP"."MTSEL": generation complete (429 ms)
Thu Dec 02 21:02:32 CET 2010 Thread[TestRunner-Thread,5,main] {istat} stopping 
daemon, active=false [q/p/s=0/1/1,err:k/u=0/0,rej=337]

BTW, I find the "daemon stats" to be a bit messy. Any ideas how to improve the 
presentation?
Is it too much info?
Anything you miss?
It will only be printed when the database is properly shut down.

Here's a quick legend:
 active = whether the daemon was doing work when stopped
 q = queued
 p = processed
 s = scheduled
 k = known errors (expected)
 u = unexpected errors
 rej = rejected requests (full queue or duplicate entries)

I'll address Dag's comments in the next patch.


> Continue investigation of automatic creation/update of index statistics
> -----------------------------------------------------------------------
>
>                 Key: DERBY-4771
>                 URL: https://issues.apache.org/jira/browse/DERBY-4771
>             Project: Derby
>          Issue Type: Task
>          Components: SQL, Store
>    Affects Versions: 10.8.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: autoindexstats.html, 
> derby-4771-1a-prototype_code_dump.diff, 
> derby-4771-1a-prototype_code_dump.stat, 
> derby-4771-1b-prototype_code_dump.diff, 
> derby-4771-2a-prototype_lcc_code_dump.diff, 
> derby-4771-2b-prototype_lcc_code_dump.diff, 
> derby-4771-2c-prototype_lcc_code_dump.diff, 
> derby-4771-2d-prototype_lcc_code_dump.diff, DERBY-4771-2e-prototype.rar, 
> derby-4771-2e-prototype_lcc_code_dump.diff, 
> Derby-4771-2f-AutomaticIndexStatisticsTest_wondows7.rar, 
> derby-4771-2f-prototype_lcc_code_dump-WORK-IN-PROGRESS.diff, 
> derby-4771-2f-prototype_lcc_code_dump.diff, derby.log, error-stacktrace.out, 
> rjall.out, rjall.out, rjall.out, rjall.rar, rjone.out
>
>
> Work was started to improve Derby's handling of index statistics. This issue 
> tracks further discussion and work for this task.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to