Home/ Questions/Q 136011
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T06:52:52+00:00

I am working on an app that will need to handle very large numbers.

  • 0

I am working on an app that will need to handle very large numbers.

I checked out a few available LargeNumber classes and have found a few that I am happy with. I have a class for large integers and for large floating point numbers.

Since some of the numbers will be small and some large the question is whether it is worth checking the length of the number and if it is small use a regular C# int or double and if is is large use the other classes I have or if I am already using the Large Integer and Large Float classes I should just stick with them even for smaller numbers.

My consideration is purely performance. Will I save enough time on the math for the smaller numbers that it would be worthwhile to check each number after is is put in.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Really hard to tell – Depends on your 3rd party libraries 🙂

    Best bet would be to use the System.Diagnostics.StopWatch class, do a gazzillion different calculations, time them and compare the results, I guess ..

    [EDIT] – About the benchmarks, I’d do a series of benchmarks your largeInt-type to do the calculations on regular 32/64 bits numbers, and a series checking if the number can fit in the regular Int32/Int64 types (which they should), ‘downcasting’ them to these types, and then run the same calculations using these types. From your question, this sounds like what you’ll be doing if the built-in types are faster..

    If your application is targetted for more people than yourself, try to run them on different machines (single core, multicore, 32bit, 64bit platforms), and if the platform seems to have a large impact in the time the calculations take, use some sort of strategy-pattern to do the calculations differently on different machines.

    Good luck 🙂

    • 0