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.
Post History
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 p...
Answer
#5: Post edited
by
jla
·
2020-08-21T07:58:09Z (about 4 years ago)
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 backend 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.
- 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.
#4: Post edited
by
jla
·
2020-08-21T07:57:25Z (about 4 years ago)
- 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 backend 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.Ultimately such savings will be minute and should usually 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.
- 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 backend 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.
#3: Post edited
by
jla
·
2020-08-21T07:35:19Z (about 4 years ago)
- 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 backend 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.
Ultimately such savings will be minute and should usually 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 backend performance.
- 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 backend 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.
- Ultimately such savings will be minute and should usually 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.
#2: Post edited
by
jla
·
2020-08-21T07:34:01Z (about 4 years ago)
- 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 backend is.
Some backend 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.- Ultimately such savings will be minute and should usually 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 backend performance.
- 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 backend 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.
- Ultimately such savings will be minute and should usually 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 backend performance.
#1: Initial revision
by
jla
·
2020-08-21T07:31:19Z (about 4 years ago)
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 backend is. Some backend 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. Ultimately such savings will be minute and should usually 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 backend performance.