ailabs-software/gist:8834a9cc945cb234130113c1d9b66069

## gistfile1.txt
1) Needs more RAM (swap is 1.6GB often times)
2) Disc is getting too full (82%), causing more SSD garbage collection/moving stuff around on disc.
3) Not enough cores to handle 100 max_connections -- intrbiz says look at adding cores first as your load average is over core count.
4) Application processes stealing CPU from postgres
5) Poorly designed queries -- peerce
    Intrbiz says: Log only slow queries so you can get an idea if it is certain queries which are consistently slow.
6) A possible change is that we are getting a lot of concurrent visits putting strain on the system through analytics caused by bots/spam filters visiting all links at once. We have been seeing that this results in a bunch of INSERT queries getting stuck running for many seconds. Do we need to change the isolation level so these INSERT queries can run smoothly concurrently?
	1) Needs more RAM (swap is 1.6GB often times)
	2) Disc is getting too full (82%), causing more SSD garbage collection/moving stuff around on disc.
	3) Not enough cores to handle 100 max_connections -- intrbiz says look at adding cores first as your load average is over core count.
	4) Application processes stealing CPU from postgres
	5) Poorly designed queries -- peerce
	Intrbiz says: Log only slow queries so you can get an idea if it is certain queries which are consistently slow.
	6) A possible change is that we are getting a lot of concurrent visits putting strain on the system through analytics caused by bots/spam filters visiting all links at once. We have been seeing that this results in a bunch of INSERT queries getting stuck running for many seconds. Do we need to change the isolation level so these INSERT queries can run smoothly concurrently?