2eight7

2-eight-7When I was writing my post yesterday I was reflecting on how much time we were spending making our code int friendly — specifically, dealing with the problems when you’re working with values around Integer.MAX_VALUE or 2147483647 (231-1). I likened it to i18n (internationalization) or l10n (localization). Much in that same vein, I’d like to coin the term “2eight7” to represent the problems one runs into when working with a signed integer and any code that depends (implicitly or explicitly) on it.

Let the debates begin!

Comments

  1. Mohammed Adnan says:

    In what ways do you run into this problem? When assigning a number to each data element? Or summing the number of times a data element is identified or mapped for a MapReduce?

  2. Here at AK we count *a lot*. We get billions of requests a day on typically hundreds of millions of keys. All of our counters, sketches, hash tables, etc need to allow for billions of elements. Our map-reduce jobs operate on hundreds of billions of rows. In all of this, its really easy to overflow an integer counter and not know it.

    Let me know how I can be more specific!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: