Jump to content

Erik@Grijjy

Members
  • Content Count

    30
  • Joined

  • Last visited

  • Days Won

    5

Erik@Grijjy last won the day on May 5

Erik@Grijjy had the most liked content!

Community Reputation

96 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have attached a spreadsheet I created a couple of years ago, comparing DD and QD to Single and Double, as well as to some well-known arbitrary precision libraries. Results may be a bit different now if I would run these tests again, but I think will still be in the same ballpark. In short, DD is 2-10 times slower than Double, but 5-100 times faster than other arbitrary precision libraries using the same precision. Likewise, QD is 4-100 times slower than Double, but 5-250 times faster than other libraries. You can also do some simple benchmarking by running the included Mandelbrot sample at different levels of precision (for a magnification level that works at Double precision). Since this library directly uses the QD C++ library, it has the same limitations (such as thread safety). Although I would assume that most operations would be thread safe since as long as you don't mutate the same DD/QD value from multiple threads. But I haven't checked the C++ source code for this, so I am not sure. MultiPrecisionSpeed.xlsx
  2. Need more precision than Single and Double can provide? Then maybe this will help: https://blog.grijjy.com/2021/05/05/high-precision/
  3. Growing impatient while building your FireMonkey app for macOS, iOS or Android? This post shows a way to (significantly) decrease the amount of time it takes for your app to build on these platforms. https://blog.grijjy.com/2021/04/05/build-speed/
  4. We have open sourced our Deployment Manager to simplify deployment of a large number of files or folders to iOS or Android. https://blog.grijjy.com/2021/02/07/deployman/
  5. Get the most out of your GPU by writing custom shaders for FireMonkey! https://blog.grijjy.com/2021/01/14/shader-programming/
  6. Erik@Grijjy

    An XML DOM with just 8 bytes per node

    True, but for such small DOMs, memory isn't the issue anyway, so the overhead is negligible. Although you still get the advantage of reduced memory fragmentation though...
  7. Delphi 10.4 (finally) switched to a new version of the Android NDK. The GNU-STL had been deprecated for a long time, and Delphi finally switched to libc++. Thanks for pointing this out. I will make the change in the official repo.
  8. Erik@Grijjy

    An XML DOM with just 8 bytes per node

    Then maybe now is a good time to upgrade to the latest Delphi version😉
  9. Erik@Grijjy

    An XML DOM with just 8 bytes per node

    Your wish is my command. Guess I was a bit lazy earlier... Pushed an updated for this.
  10. Erik@Grijjy

    An XML DOM with just 8 bytes per node

    Glad you like it, and thanks for pointing out this issue. It only happens when you compile with Overflow Checking turned on. The hash functions I use should be compiled with overflow checking turned off, so I just added an {$OVERFLOWCHECKS OFF} directive to the Neslib.Xml.Types unit. Could you pull the latest version and try again?
  11. Erik@Grijjy

    An XML DOM with just 8 bytes per node

    Happy to hear! Don't know about creating a memory manager though. Very advanced stuff. And there are already some pretty good 3rd party memory managers out there. Although it would be nice to have a high performance memory manager for mobile platforms as well. Maybe something like Microsoft's Mimalloc.
  12. Erik@Grijjy

    An XML DOM with just 8 bytes per node

    Glad you like it! Could be interesting to see if this can by applied to JSON as well. Wouldn't want to break the existing API though...
  13. Check out some of the interesting algorithms and data structures used to create an extremely light-weight XML DOM. https://blog.grijjy.com/2020/10/07/an-xml-dom-with-just-8-bytes-per-node/
  14. Another post about Custom Managed Records. This time, this new language feature is used to create smart pointers. https://blog.grijjy.com/2020/08/12/custom-managed-records-for-smart-pointers/
  15. @Stefan Glienke I agree that the implementation is lacking and would like to see a more C++ like implementation. And it would be great if you could overload the "." or "^" operator. That being said, the current implementation still has its uses...
×