I am sure my wife will be very happy to learn about this test. It will definitely make up for our insurance going from about $12K per year to $26K per year. That, along with keeping our doctor and saving $2,500 per year have been fantastic. News Flash: Engineers think technology while, in the real world, the problem has nothing whatsoever to do with it. It's like tuning your Ferrarri for more power while your reality…
A Billion User Load Test on Healthcare.gov
41–50 of 93 posts
Re: A Billion User Load Test on Healthcare.gov
#42Earlier quoted context omitted.
Now we see the real test of whether healthcare.gov has reached the level of consumer tech: Does bug-report-via-top-ranked-HN-comment get anything done?
AFAICT it's actually a Cigna bug report yeah? Happy to make sure it gets to the right place if I'm wrong. (/me doesn't work for nava, does work on healthcare.gov)
Re: A Billion User Load Test on Healthcare.gov
#43IAM: Identity and Access Management
Forgerock: https://www.forgerock.com/
Re: A Billion User Load Test on Healthcare.gov
#448K transactions / second is hardly extreme load. It's good they can support it, and I doubt they need more, but many, many sites handle more load than that.
The numbers that were asked for were 12k/auth per second during peak time for the Italians.
The British wasn't clear but it hinted at 0.1% of user authenticating per second, which is about the same range. (The numbers of users itself was not defined, it depends on who would join the program).
SLA: 1500 ms for the account verification. 150 ms for most operations. (Some more time when requesting optional attributes like name/address/phone)
If this interests you, I've published a few numbers I got from preliminary testing (to determine whether we could answer the RFP or not): https://thehftguy.com/2015/10/23/10-millions-users-accounts-...
Re: A Billion User Load Test on Healthcare.gov
#45I am sure my wife will be very happy to learn about this test. It will definitely make up for our insurance going from about $12K per year to $26K per year. That, along with keeping our doctor and saving $2,500 per year have been fantastic. News Flash: Engineers think technology while, in the real world, the problem has nothing whatsoever to do with it. It's like tuning your Ferrarri for more power while your reality…
Re: A Billion User Load Test on Healthcare.gov
#46I wonder if this healthcare.gov will exist a year from now. It is nice to see how far it has come in 2 years.
Personally I preferred the previous way of signing up for coverage ... call up a private insurer and sign up? The cost was less too as I wasn't paying for insurance for lazy sally or Joe Schmoe! So for me Obamacare/social medicine forced those who do and work to pay and cover for those who don't. See ya Obamacare(love obama though).
Also the $300 plan I paid each month for sucked.. they fought me tooth and nail to cover things my doc prescribed.. I.e. Various scans(cat scan, etc).
Re: A Billion User Load Test on Healthcare.gov
#47Earlier quoted context omitted.
Insurance companies don't insure the unemployed for free. They're either paying their own premiums, or they're on medicaid/medicare. If they're on medicaid, it was paid for by the state/fed government from taxes... not from insurance premiums paid by someone else.
The cost of Medicaid and Medicare may show up in insurance premiums. http://kff.org/report-section/uncompensated-care-for-the-uni... There are other discussions of cost shifting that will make more aggressive claims; I've chosen to link Kaiser Family Foundation because I think they are pretty credible.
Re: A Billion User Load Test on Healthcare.gov
#48Earlier quoted context omitted.
The cost of Medicaid and Medicare may show up in insurance premiums. http://kff.org/report-section/uncompensated-care-for-the-uni... There are other discussions of cost shifting that will make more aggressive claims; I've chosen to link Kaiser Family Foundation because I think they are pretty credible.
the amount potentially associated with uncompensated care cost shifting is only 2.3 percent of private health insurance costs in 2013.
But the $21.1 billion out of $84.9 billion is a pretty big chunk of the unmet costs.
Re: A Billion User Load Test on Healthcare.gov
#49Earlier quoted context omitted.
True, but running at 7754 tps over an hour with a database of 28M users is easier than with a database of 1B users.
It is much easier to test with a small # of active users and a large (mostly unused) database, than with a large # of active users. To me the title implies 1B active users ("billion user load test").
If you have many active users, you're testing for the write load of user tokens and sessions.
If you have many accounts, you're testing for the read load of the account database.
Technically speaking, user id and sessions should be two different database systems, because they have different requirements and they're conflicting.
For the first one, the problem is to have lots of write and enough performances. Plus having the storage if you keep tokens forever (typical for auditing).
For the second one, the problem is to be able to store all the accounts, plus read performances (which can always be hacked by adding layers of caching).
Funfact: if each account is only email + password (64 + 64 char), 1 billion accounts consume 128 GB, just for storing the ASCII characters. A lot more in practise with metadata, empty space and other fields.
They say that they only had 1 maria DB on a single EBS P-IOPS volume. That's kinda weird that a 1 billion users database could fit in that -and zero errors, really?-. Maybe they just had a single integer field (1,2,3,4) to define the user and the password :D
Re: A Billion User Load Test on Healthcare.gov
#50Earlier quoted context omitted.
AFAICT it's actually a Cigna bug report yeah? Happy to make sure it gets to the right place if I'm wrong. (/me doesn't work for nava, does work on healthcare.gov)
There is a persistent error message on my 2016 profile on healthcare.gov after that button was clicked (despite it also showing it's active on that side of things). My understanding is that the bug is the integration point between the two. From past issues and what I've been told on this one, is that the only way things get fixed and made right is to have healthcare.gov retransmit the correct data/status. Cigna can't…