-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The cancer is gone -- phase 1 #38
base: master
Are you sure you want to change the base?
Conversation
- local_postgres_data:/var/lib/postgresql/data | ||
- local_postgres_data_backups:/backups | ||
- local_postgres_data:/var/lib/postgresql/data:cached | ||
- local_postgres_data_backups:/backups:cached |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How often is the backup updated. Does it make sense to cache it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I'm totally honest, I have no idea. According to that article, the difference should be imperceptible to the user. I haven't really pushed on it that much but after I did this (and restarted Docker) it really improved the performance.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to say to uncache the backups but keep postgresql cached, since the backup isn't read from very often.
Hahahahahahaha nice. Looks great |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like these changes a lot
- local_postgres_data:/var/lib/postgresql/data | ||
- local_postgres_data_backups:/backups | ||
- local_postgres_data:/var/lib/postgresql/data:cached | ||
- local_postgres_data_backups:/backups:cached |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to say to uncache the backups but keep postgresql cached, since the backup isn't read from very often.
I want to wait to merge this until phase 2 is done so that there isn't confusion about duplicate phone number fields |
Totally agree |
Phase 1 generates a new class,
PatientPhoneNumber
, that represents a phone number for a patient. Adding phone numbers is now done with a '+' sign on the patient detail view.Phase 2 will actually remove the old phone numbers, after we copy everything over using the python shell.
PatientPhoneNumber
with link toPatient
objectphone_number
toUser
PatientPhoneForm
,phonenumber_field
for handling phone numbers.PHONENUMBER_DEFAULT_REGION
controls default country codelocal.yml
to adddelegated
,cached
maybe improving MacOS performance?