Currently I am borrowing java.math.BigInteger from the J# libraries as described here. Having never used a library for working with large integers before, this seems slow, on the order of 10 times slower, even for ulong length numbers. Does anyone have any better (preferably free) libraries, or is this level of performance normal?
views:
8722answers:
11
+2
A:
I'm not sure about the performance, but IronPython also has a BigInteger class. It is in the Microsoft.Scripting.Math namespace.
Daniel Plaisted
2008-10-07 00:20:52
+1
A:
Yes, it will be slow, and 10x difference is about what I'd expect. BigInt uses an array to represent an arbitrary length, and all the operations have to be done manually (as opposed to most math which can be done directly with the CPU)
I don't even know if hand-coding it in assembly will give you much of a performance gain over 10x, that's pretty damn close. I'd look for other ways to optimize it--sometimes depending on your math problem there are little tricks you can do to make it quicker.
Bill K
2008-10-07 00:23:35
A:
I used Biginteger at a previous job. I don't know what kind of performance needs you have. I did not use it in a performance-intensive situation, but never had any problems with it.
Jason Jackson
2008-10-07 00:29:04
+2
A:
This may sound like a strange suggestion, but have you tested the decimal type to see how fast it works?
The decimal range is ±1.0 × 10^−28 to ±7.9 × 10^28, so it may still not be large enough, but it is larger than a ulong.
There was supposed to be a BigInteger class in .NET 3.5, but it got cut.
R. Bemrose
2008-10-07 00:31:26
Yes, I saw that anouncement when originally looking for a BigInt library. Makes me sad. Oh well.
Matthew Scharley
2008-10-07 00:34:10
You would have to be careful - using a decimal might cause rounding issues.
Blorgbeard
2008-10-07 00:40:21
Decimal doesn't cause rounding errors. It's not floating point.
Kibbee
2008-10-07 00:57:09
Decimal isn't float. It's a precision type as far as I'm aware.
Matthew Scharley
2008-10-07 00:57:17
Decimal only tries to minimize errors due to rounding. It is not immune to rounding. http://msdn.microsoft.com/en-us/library/system.decimal.aspx
Robert Paulson
2008-10-07 01:48:17
Decimal *is* a floating point type. It's just that it's a floating decimal point instead of a floating binary point.See http://pobox.com/~skeet/csharp/decimal.htmlI wouldn't expect rounding issues if all values are integers within the appropriate range though.
Jon Skeet
2008-10-07 06:10:16
+4
A:
I reckon you could optimize the implementation if you perform all the operations on BigInts that are going to return results smaller than a native type (Eg. int64) on the native types and only deal with the big array if you are going to overflow.
edit This implementation on codeproject, seems only 7 times slower ... But with the above optimization you could get it to perform almost identically to native types for small numbers.
Sam Saffron
2008-10-07 00:33:45
I believe the J# library uses Byte's internally, it has a ToByteArray() function atleast, and no other ToArray() function. This might be an idea if I wanted to roll my own, I'm not too thrilled with that idea either though.
Matthew Scharley
2008-10-07 00:37:28
What size data are you working with, in general? Will stuff overflow the Int64 size on a regular basis, or is it an exception?
Sam Saffron
2008-10-07 00:44:45
I'm doing it mostly on a case by case basis, setting it to BigInt when I run into an overflow with a checked{} block. If it does that once, then there's a pretty good chance it'll do it repeatedly and often.
Matthew Scharley
2008-10-07 00:58:18
monoxide, I don't think it will be easy to get this to perform much faster than the implementation on codeproject for large numbers.
Sam Saffron
2008-10-07 01:35:50
Like I said in my original post, I've never used a BigInteger implementation before, so I wouldn't know what sort of performance they get. That was more the question I was asking. Damn, I still want to roll my own as an intellectual excercise now though :(
Matthew Scharley
2008-10-07 02:13:38
+1
A:
This won't help you, but there was supposed to be a BigInteger class in .Net 3.5; it got cut, but from statements made at PDC, it will be in .Net 4.0. They apparently have spent a lot of time optimizing it, so the performance should be much better than what you're getting now.
Further, this question is essentially a duplicate of http://stackoverflow.com/questions/25375/how-can-i-represent-a-very-large-integer-in-net
technophile
2008-11-08 20:41:33
BigInteger is in 3.5 but its an internal class. ;) Its there just not ready for prime time.
Ray Booysen
2009-01-31 13:25:59
+1
A:
See the answers in this thread. You will need to use one of the third-party big integer libraries/classes available or wait for C# 4.0 which will include a native BigInteger datatype.
Scott Dorman
2008-11-10 20:28:47
+26
A:
MS is going to introduce System.Numerics.BigInteger class in .NET 4.0
Until then, look at IntX class.
IntX is an arbitrary precision integers library written in pure C# 2.0 with fast - O(N * log N) - multiplication/division algorithms implementation. It provides all the basic operations on integers like addition, multiplication, comparing, bitwise shifting etc.
Davorin
2009-04-27 19:06:08
+4
A:
The System.Numerics.BigInteger class in .NET 4.0 is based on Microsoft.SolverFoundation.Common.BigInteger from Microsoft Research.
The Solver Foundation's BigInteger class looks very performant. I am not sure about which license it is released under, but you can get it here (download and install Solver Foundation and find the Microsoft.Solver.Foundation.dll).
Rasmus Faber
2009-06-19 17:48:05
+2
A:
Here are several implementations of BigInteger in C#. I've used Mono's BigInteger implementation, works pretty fast (I've used it in CompactFramework)
Vadmyst
2009-06-23 09:48:40