I still seem to have a problem with slow mining using merge mining as it's taken 7 hours to get this 2011-08-14T10:09:41.168619,solve,0,0,1,1,1

I've got many of these 2011-08-14T09:53:57.364787,solve,0,0,0,1,1

the "difficulty" : 0.06198025, one the 2nd aux in this case mm2TEST should not have taken 7 hours

this is with 270kh/sec miner

I see no errors but it just seems very slow to mine

;;bc,calcd 270 0.061 shows it I should get gribble: The average time to generate a block at 270 Khps, given the supplied difficulty of 0.061, is 16 minutes and 10 seconds

I used this in the proxy line:

/home/sacarlson/Downloads/mmproxy --parent-url

http://yourusername:yourpassword@127.0.0.1:48332/ --aux-url

http://yourusername:yourpassword@127.0.0.1:10332/ http://yourusername:yourpassword@127.0.0.1:12332/ http://yourusername:yourpassword@127.0.0.1:14332/ http://yourusername:yourpassword@127.0.0.1:13332/ --merkle-size 4 -w 9992

This is using MultiCoin-exp that uses your merged code for merge mining with test chain configs, bitcoin.conf.namecoin diff 94035.90217415 as parent, aux1 beerA difficulty 50.0, aux2 mm2TEST diff 0.06198025, aux3 mm4TEST diff 0.01475864, aux4 mm3TEST diff 0.00441692,

anyone else getting slow results with merge mining test or did i configure something wrong or maybe my code problems? I'll try some simpler experments with just a parent and 1 aux to take a closer look at results, some details of how I setup can be seen

http://bitcointalk.org/index.php?topic= ... #msg394289 I'm using my latest Multicoin-exp release in github

Update 8/15/11 10:58am BKK:

I ran another merge mine experiment of just parent and one aux with new difficulties parent of .062 and aux chain diff .010

experment ran with 280kh/sec run from 15:07 block2 to 3:25 block 52 = about 14.4minits per block on both parent and aux chain

So the good news is I get about what I would expect on the parent chain ;;bc,calcd 280 0.062

gribble: The average time to generate a block at 280 Khps, given the supplied difficulty of 0.062, is 15 minutes and 51 seconds

The bad news is I don't get as much as I would expect from the aux chain. I just don't have a full understanding why.

;;bc,calcd 280 0.010

gribble: The average time to generate a block at 280 Khps, given the supplied difficulty of 0.010, is 2 minutes and 33 seconds

sample as seen from proxy:

2011-08-14T15:07:12.921571,solve,1,1

2011-08-14T15:08:53.573864,solve,1,1

2011-08-14T15:32:25.379898,solve,1,1

2011-08-14T15:44:39.154894,solve,1,1