Closed YazeedLoonat closed 4 months ago
Name | Link |
---|---|
Latest commit | 26dd612c627ad821818164d6ad5840de709cff37 |
Latest deploy log | https://app.netlify.com/sites/partners-bloom-dev/deploys/667c4f39a6c53c0008739280 |
Deploy Preview | https://deploy-preview-4159--partners-bloom-dev.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Name | Link |
---|---|
Latest commit | 26dd612c627ad821818164d6ad5840de709cff37 |
Latest deploy log | https://app.netlify.com/sites/bloom-exygy-dev/deploys/667c4f39d7a5e20008d93a97 |
Deploy Preview | https://deploy-preview-4159--bloom-exygy-dev.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Have you had the opportunity to performance test this?
Hey @emilyjablonski because of your comment I changed a few things. The biggest change is how we were inserting the application lottery order into the database. Before it was doing 1 write per application + 1 write per application where a preference was claimed
which could be A LOT of writes to the databse.
I switched it to use a createMany()
call instead so now there is 1 write for all the applications, and 1 write per preference on the listing which is WAY WAY down
excellent call out!
I haven't been able to truly load test this since its not really attached to any endpoints quite yet, but that will definitely need to happen when we go to create the endpoints
Hey @mcgarrye made updates and left you some comments back, lemme know what you think
Hey @mcgarrye made updates and left you some comments back, lemme know what you think
Looks great
Hey @ludtkemorgan made some updates per your comments, if you wanna take a lil peek and then we can switch the label and merge this in!
This PR addresses https://github.com/bloom-housing/bloom/issues/4055
Description
This adds the randomizer for lottery to the csv export it doesn't expose a way to do this, but there are unit tests to demo how it'll work
How Can This Be Tested/Reviewed?
the endpoints and stuff are coming in a part 2, this is just the randomization logic and unit tests
Author Checklist:
yarn generate:client
and/or created a migration when requiredReview Process: