Timeline for Is object pooling a deprecated technique?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2018 at 4:48 | history | edited | user204677 | CC BY-SA 3.0 | deleted 8291 characters in body |
| Dec 20, 2017 at 15:52 | history | edited | marstato | CC BY-SA 3.0 | Restored previous version |
| Dec 20, 2017 at 15:41 | review | Low quality posts | |||
| Dec 20, 2017 at 15:52 | |||||
| Dec 20, 2017 at 15:32 | history | edited | user204677 | CC BY-SA 3.0 | deleted 8441 characters in body |
| May 4, 2017 at 19:34 | comment | added | strickli | Excellent answer, and cogent. I'd add (perhaps, maybe as an asterisk?) that the "24 bytes" claim refers to 4 instances of 4-byte floats (16 bytes), plus 4 bytes for the object reference, plus 4 bytes for a lock reference. This is the exact overhead your design eliminates. | |
| Jan 1, 2016 at 13:46 | history | edited | user204677 | CC BY-SA 3.0 | added 12 characters in body |
| Jan 1, 2016 at 12:03 | history | edited | user204677 | CC BY-SA 3.0 | added 238 characters in body |
| Jan 1, 2016 at 11:55 | history | edited | user204677 | CC BY-SA 3.0 | added 597 characters in body |
| Jan 1, 2016 at 9:16 | history | edited | user204677 | CC BY-SA 3.0 | added 376 characters in body |
| Jan 1, 2016 at 9:11 | history | answered | user204677 | CC BY-SA 3.0 |