By: -.- (blarg.delete@this.mailinator.com), May 30, 2022 2:44 am
Room: Moderated Discussions
Michael S (already5chosen.delete@this.yahoo.com) on May 30, 2022 1:32 am wrote:
> I am old-fashioned. Never believed in principles of Doug McIlroy.
> IMHO, if for your workload JSON parsing can be measurably sped up by SIMD and if this speed
> up is noticeable in time profile of the whole app then it means one thing - you need something
> better than JSON as your storage/COMM format. Start rearchitecting now and you will be
> regarded in the future. That is, if you're not shown the door before that.
Good luck convincing every third party service out there to adopt your "better than JSON" serialization.
This also ignores the fact that JSON is efficient in certain environments (e.g. browser Javascript).
And why does it have to be a "noticeable" improvement? I like faster code, and I'm sure many others do as well. If it makes the application 1% faster, then why not? Across a large enough scale, 1% can mean a lot - for $100M in servers, 1% is ~$1M in potential savings. And if you consider how prevalent JSON is, it makes sense to eke out as much performance due to aggregate benefits, even if, individually, it doesn't matter much.
> I am old-fashioned. Never believed in principles of Doug McIlroy.
> IMHO, if for your workload JSON parsing can be measurably sped up by SIMD and if this speed
> up is noticeable in time profile of the whole app then it means one thing - you need something
> better than JSON as your storage/COMM format. Start rearchitecting now and you will be
> regarded in the future. That is, if you're not shown the door before that.
Good luck convincing every third party service out there to adopt your "better than JSON" serialization.
This also ignores the fact that JSON is efficient in certain environments (e.g. browser Javascript).
And why does it have to be a "noticeable" improvement? I like faster code, and I'm sure many others do as well. If it makes the application 1% faster, then why not? Across a large enough scale, 1% can mean a lot - for $100M in servers, 1% is ~$1M in potential savings. And if you consider how prevalent JSON is, it makes sense to eke out as much performance due to aggregate benefits, even if, individually, it doesn't matter much.