Marti Martz

@Joeviocoe > AWS not Mongo? See https://github.com/OpenUserJS/OpenUserJS.org/issues/1548#issuecomment-447667327 for the breakdown of which one is which. Both IPs that we connect to are Amazon IPs though which I didn't know until...

#### Misc log note Most recent, and only on this server restart, log message: ``` console 2018-12-19 05:07:22.573 +00:00: { MongoNetworkError: connection 2 to *clipped*.mongolab.com:43493 timed out at Socket. (~/OpenUserJS.org2/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:259:7)...

@Joeviocoe With my edited test results up [there](https://github.com/OpenUserJS/OpenUserJS.org/issues/1548#issuecomment-448471466) the one with no content is fatal to end users. Until this is resolved the site is offline. I've put the parking...

Well here's local pro, at current project HEAD, on how I see it. I'm the only user connected to the DB's right now and it is full speed. Doing this...

We're in RO script storage mode. See https://openuserjs.org/about for site status messages. Will see when this starts to lag for me.

Already lagging... That was quick.

#### Misc log note ``` console > db['bruteforce-store'].count() 2727 ``` That's since yesterday of unique IPs... so it's well below the threshhold when we were encountering a .user.js engine malfunction...

#### Misc log note Manually changed `poolSize` to `2` since my last comment and get these: stderr: ``` console 2018-12-19 10:29:30.828 +00:00: MongoDB connection is disconnected 2018-12-19 10:29:30.831 +00:00: MongoDB...

Change in site response... pending...

And change back... had about 4 minutes of sheer bliss where it was full speed on pro... however back to lagging... UGGH.