mount -t cifs -o username=ives,password=<passwd>,uid=ives,gid=ives //ix/users/Ives/stage /stage
This obviously doesn't work if I'm not in the same network (I don't feel like setting up a VPN).
Now, for the worse news: I ran the benchmark again earlier this week, with the following raw results:
JavaPriorityQueue;10000;6561024477
JavaPriorityQueue;10000;5404055641
JavaPriorityQueue;10000;5448148997
JavaPriorityQueue;10000;5518502627
JavaPriorityQueue;10000;5400359276
JavaPriorityQueue;10000;5430126603
JavaPriorityQueue;10000;5759644066
JavaPriorityQueue;10000;5401271246
JavaPriorityQueue;10000;5464453238
JavaPriorityQueue;10000;5407788605
PairingHeapQueue;10000;5446775232
PairingHeapQueue;10000;5423628469
PairingHeapQueue;10000;5418897748
PairingHeapQueue;10000;5421841291
PairingHeapQueue;10000;5409722011
PairingHeapQueue;10000;5729907979
PairingHeapQueue;10000;5416062530
PairingHeapQueue;10000;5477439257
PairingHeapQueue;10000;5433077898
PairingHeapQueue;10000;5412777948
TreeMapQueue;10000;5425671545
TreeMapQueue;10000;5426851101
TreeMapQueue;10000;5425298384
TreeMapQueue;10000;5399660301
TreeMapQueue;10000;5392418944
TreeMapQueue;10000;5391327447
TreeMapQueue;10000;5926422059
TreeMapQueue;10000;5393873311
TreeMapQueue;10000;5443363135
TreeMapQueue;10000;5744871062
SkipList;10000;5397133306
SkipList;10000;5675809273
SkipList;10000;5422119755
SkipList;10000;5392720363
SkipList;10000;5400829320
SkipList;10000;5422794354
SkipList;10000;5415324309
SkipList;10000;7051620337
SkipList;10000;5416224427
SkipList;10000;5420276478
SplayTreeQueue;10000;5395243251
SplayTreeQueue;10000;5412487676
SplayTreeQueue;10000;5545716916
SplayTreeQueue;10000;5442838378
SplayTreeQueue;10000;5430914414
SplayTreeQueue;10000;5610695557
SplayTreeQueue;10000;5464748603
SplayTreeQueue;10000;5408613093
SplayTreeQueue;10000;5501706374
SplayTreeQueue;10000;5405540312
HashMapQueue;10000;5396951336
HashMapQueue;10000;5384225368
HashMapQueue;10000;5393222775
HashMapQueue;10000;5398562791
HashMapQueue;10000;5368138462
HashMapQueue;10000;5419371366
HashMapQueue;10000;5769373695
HashMapQueue;10000;5489567527
HashMapQueue;10000;5438062242
HashMapQueue;10000;5873245080
EncapsulatedSkipList;10000;5621653702
EncapsulatedSkipList;10000;5439568704
EncapsulatedSkipList;10000;5412919542
EncapsulatedSkipList;10000;5461816898
EncapsulatedSkipList;10000;5462168806
EncapsulatedSkipList;10000;5402203002
EncapsulatedSkipList;10000;5425761816
EncapsulatedSkipList;10000;5393928593
EncapsulatedSkipList;10000;5490411424
EncapsulatedSkipList;10000;5548951710
FibonacciHeapQueue;10000;5666839845
FibonacciHeapQueue;10000;6225841498
FibonacciHeapQueue;10000;5429501483
FibonacciHeapQueue;10000;5423790030
FibonacciHeapQueue;10000;5815081783
FibonacciHeapQueue;10000;5437626501
FibonacciHeapQueue;10000;5462466700
FibonacciHeapQueue;10000;5400344311
FibonacciHeapQueue;10000;5480721465
FibonacciHeapQueue;10000;5426114305
CalendarQueue;10000;5380552101
CalendarQueue;10000;5488739278
CalendarQueue;10000;5993241530
CalendarQueue;10000;5388830581
CalendarQueue;10000;5406325242
CalendarQueue;10000;5446190891
CalendarQueue;10000;5401955885
CalendarQueue;10000;5407636115
CalendarQueue;10000;5406300099
CalendarQueue;10000;5422167002
EventHeapQueue;10000;5700755620
EventHeapQueue;10000;5400055933
EventHeapQueue;10000;4371602178
EventHeapQueue;10000;4549412219
EventHeapQueue;10000;6803269647
EventHeapQueue;10000;5401834240
EventHeapQueue;10000;5759731649
EventHeapQueue;10000;5439161377
EventHeapQueue;10000;5446489216
EventHeapQueue;10000;4398517379
.
This translates to the following relative results:
| CalendarQueue | 99.2563918127% |
| HashMapQueue | 99.4717906758% |
| SkipList | 99.4884038778% |
| PairingHeapQueue | 99.5499291959% |
| TreeMapQueue | 99.5874295653% |
| EventHeapQueue | 99.8350335131% |
| SplayTreeQueue | 99.9025243435% |
| JavaPriorityQueue | 100.0% |
| EncapsulatedSkipList | 100.250872379% |
| FibonacciHeapQueue | 100.262799402% |
The next step will be to see what's taking up time in a profiler and increasing the time limit a single experiment can take.
Hi Ives,
BeantwoordenVerwijderenNatuurlijk cruciaal dat je de runtime van je experiment verhoogd om tot zinvolle resultaten te komen.
Verder een goed idee om initialisatie tijd niet mee te nemen in je tijdsmeting.
mvg,
Kurt
Uhu, ik had dit gisteren al eens met veel (15x ofzo) hogere runtimes geprobeerd en dan leek ik betere resultaten uit te komen. Initialisatie niet in de meting opnemen had ik nog niet geprobeerd, ik zal eens kijke hoe ik dit kan implementeren (proper of minder proper).
VerwijderenIk had wel nog een vreemd probleem: af en toe dan komt niet alle output op het einde van een experiment "erdoor". Ik weet niet of dit een bug in mvn, ant of de simulator is, maar het gebeurt zelfs niet alleen maar met mijn custom output maar ook met logging output:
(knip)
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - SP[0]: SYS_COMPILER_TIME: 4240
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - SP[0]: SYS_THREAD_COUNT: 5
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - SP[0]: SYS_SP_COUNT: 41
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - SP[0]: SYS_SP_SYNCTIME: 1
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - SP[0]: SYS_SP_TIME: 3402
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: CORE_ID: 0
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: THREAD_NAME: Core0
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: THREAD_ID: 10
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: CREATE_TIME: 1333372117753
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: START_TIME: 1333372118220
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: EVENT_SIMPLE_COUNT: 2849596
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: EVENT_SUSP_COUNT: 1383796
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: EVENT_COUNT: 4233392
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: EVENT_EXEC_TIME: 29598
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: EVENT_QUEUE_SIZE: 640
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: MAX_EVENT_QUEUE_SIZE: 642
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: AVG_EVENT_QUEUE_SIZE: 632.6833333333333
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: ENTITY_COUNT: 64
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: UPDATE_STATS_TIME: 24
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: UPDATE_STATS_COUNT: 60
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: AVG_EVENTRATE_VTIME: 16.933568
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: AVG_EVENTRATE_TIME: 71.82788693203027
[java] 60743 [ Monitor] INFO LoggerMonitorOutput - MP[0]: AVG_VTIMERATE_TIME: 4.241745563134141
[java] 60744 [ Monitor] INFO LoggerMonitorOutput - MP[0]: CURRENT_STATE: FINISHED
[java] 60744 [ Monitor] INFO LoggerMonitorOutput - MP[0]: SIMULATION_VTIME: 250000
[java] 60744 [ Monitor] INFO LoggerMonitorOutput - MP[0]: REQUESTED_VTIME: 250000
[java] 60744 [ Monitor] INFO LoggerMonitorOutput - MP[0]: ALLOWED_VTIME: 250000
[java] 60744 [ Monitor] INFO LoggerMonitorOutput - MP[0]: ELAPSED_TIME: 58938
[java] 60744 [ Monitor] INFO LoggerMonitorOutput - MP[0]: THREAD_WAIT_TIME: 0
[java] 60744 [ Monitor] INFO LoggerMonitorOu
[INFO] Executed tasks
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:04.261s
[INFO] Finished at: Mon Apr 02 15:09:37 CEST 2012
[INFO] Final Memory: 8M/89M
[INFO] ------------------------------------------------------------------------
waardoor de totale tijd niet langer wordt geprint. Da's niet zo'n enorm probleem (mogelijk kan ik het wel met een strategisch geplaatste System.sleep() oplossen, of anders dan herhaal ik gewoon het experiment wel tot er goede output is), maar het liet mijn benchmark script crashen en ik vond het wel een vreemd probleem.
(CC:Uw email)