[bug #37494] Performance issue with NSNumber when used as key in an NSDictionary

[Richard Frith-Macdonald]

Update of bug #37494 (project gnustep):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Declined               

    _______________________________________________________

Follow-up Comment #1:

Thanks for the report, but I can't reproduce any problem ...

With the original test program, the test run was too short to give any sort of
reliable indication of the speeds of the different operations, so I increaed
the 'maxkeys' define to 10000000 (two orders of magnitude larger):

2012-10-03 14:48:30.371 nsnumberaskey[553] populating dict (low NSNumber)
2012-10-03 14:48:45.139 nsnumberaskey[553] end population of dict
2012-10-03 14:48:45.415 nsnumberaskey[553] fetching values
2012-10-03 14:48:48.778 nsnumberaskey[553] fetched values
2012-10-03 14:48:57.487 nsnumberaskey[553] populating dict (high NSNumber)
2012-10-03 14:49:12.126 nsnumberaskey[553] end population of dict
2012-10-03 14:49:12.127 nsnumberaskey[553] fetching values
2012-10-03 14:49:16.114 nsnumberaskey[553] fetched values
2012-10-03 14:49:39.502 nsnumberaskey[553] populating dict (NSString)
2012-10-03 14:50:09.438 nsnumberaskey[553] end population of dict
2012-10-03 14:50:09.438 nsnumberaskey[553] fetching values
2012-10-03 14:50:12.757 nsnumberaskey[553] fetched values

There's clearly no significant performance difference between small and large
numbers here.

Perhaps the original problem was on an old version of gnustep, or some other
issue was causing it?




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?37494>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/