Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Does using an Integer have any speed/performance benefits over a string in JSON

Parent

Does using an Integer have any speed/performance benefits over a string in JSON

+11
−0

I'm working on an API to respond some data about a bunch of orders and items.

The order and item numbers are always an integer (it's the order.id and item.id value, respectively).

Originally the response included each order number and each item number as a string, something like:

{
  "orders": [
    {
      "id": "12345",
      "item": [
        "123",
        "124",
        "125",
        "126"
      ]
    },
    {
      "id": "95812",
      "item": [
        "173",
        "198"
      ]
    }
  ]
}

I instructed the team to make the values as integers rather than strings, that exact response now looks like:

{
  "orders": [
    {
      "id": 12345,
      "item": [
        123,
        124,
        125,
        126
      ]
    },
    {
      "id": 95812,
      "item": [
        173,
        198
      ]
    }
  ]
}

My question is if there is really any purpose to what I've done? We're never going to need to perform any mathematical equations on the number, essentially they are functioning as strings (as far as I'm aware).

Perhaps it's counterproductive because now an order number cannot contain any other character besides a number - but that's anyhow how it works since it's using an INTEGER type in the database.


There's always the smaller and therefor faster response - since there's no ".
In the above example (minified) it's almost 17% smaller.

  • string = 96 bytes
  • int = 80 bytes
History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+5
−0

JSON is a standard. Performance is implementation specific and dependent on what is being done with the data. The answer really depends on what your environment is.

Some languages may have slight performance benefits from using integers when allocating memory during JSON serialisation/deserialisation. Allocating to String types might be done on the heap whereas true int types are a primitive datatype and will be allocated on the stack. Allocating memory on the heap is slower than allocation to the stack. Of course, if the JSON environment de/serialises everything on the heap then there will be practically no difference in allocation time.

Ultimately such savings will be minute and should probably be considered premature optimisation. Deciding whether to use strings or ints will likely have far more profound effects on development time and code robustness than performance.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

General comments (1 comment)
General comments
meriton‭ wrote over 3 years ago

It seems weird to focus on allocation times when discussing network I/O. If we can wait millions of processor cycles for a network response, we can probably afford a couple hundred cycles to allocate on the heap.