[15:18:29] <moos3> question, so my three nodes all go rebooted at the same time, now the prompt says OTHER and rs.status says REMOVED. How do I fix this?
[17:46:11] <diegows> hi, is there a counter for slow queries somewhere?
[18:09:45] <TheEpitome> Hello, when I perform a "db.hosts.find({},{dmiSystem: 1, networkInterfaces: 1, lanPrint: 1, pduPorts: 1, comment: 1})" from mongo shell it returns the fields I ask for almost instantly. When I perform this same query from PHP using MongoDB\Client it takes about 5 seconds, the same amount of time as if I just ran a find() without any parameters. Any ideas?
[18:40:47] <synthmeat> StephenLynx: if i don't need any caching/authentication, are there any other (relatively) complex things remaining if i decide to roll with just node.js http for my next project? (recall that you do so)
[18:52:58] <moos3> question, so my three nodes all go rebooted at the same time, now the prompt says OTHER and rs.status says REMOVED. How do I fix this?
[18:53:10] <StephenLynx> my engine generates HTML pages
[18:53:27] <StephenLynx> so it has to get the base html from somewhere, manipulate and output the final page
[18:53:44] <StephenLynx> what I do is to load and cache the pure HTML file that will be a template
[18:53:48] <StephenLynx> create a document using jsdom
[18:59:57] <StephenLynx> so even if the generation gets a little slow, it will reach a point where tasks will be dropped left and right due to being duplicates.
[19:00:09] <StephenLynx> the more works it has to do, the less work it has to do.
[19:00:20] <StephenLynx> and these pages can return a 304.
[19:00:41] <StephenLynx> and they are also compressed.
[19:01:02] <StephenLynx> so it doesn't matter too much if the generation for them isn't too fast.
[19:01:04] <synthmeat> yeah, should throw an intereting curve in page speed x requests/time
[19:01:50] <StephenLynx> and this is what I meant about optimizing for efficiency rather than speed.
[19:02:56] <StephenLynx> not only that, but I also cache individual posts.
[19:03:08] <StephenLynx> each post have 5 different caches.
[19:03:18] <StephenLynx> because they can be presented in 5 different ways.
[19:03:46] <synthmeat> yeah, that's exactly why i want to go down to node - so i can tailor in fairly straightforward way for my use-case
[19:04:14] <StephenLynx> the part that builds the post cell checks if the proper cache exists and use it. if it doesn't, it generates the cell and caches it.
[19:04:30] <StephenLynx> completely abstracting it from parts of the code that requests the cell generation.
[19:04:49] <synthmeat> oh, some kind of reddit-like thingie?
[19:08:34] <StephenLynx> I finished adding a few features and now I'll add support for 1.7
[19:08:39] <StephenLynx> which is the beta version
[19:08:59] <synthmeat> main reason i never participated in any chan-like thing is that i can't make the sense of it, on frontend. i guess it takes a while to get used to it
[19:26:58] <synthmeat> yup. i'm hoping to learn more about what matters through this (because you learn exactly nothing but express when you use express)
[19:27:21] <StephenLynx> yeah, web frameworks are cancer.
[19:27:41] <StephenLynx> I'd have to REALLY not give a single fuck about a project if I were to ever use one.
[19:36:53] <synthmeat> i mean, i'm at age where i noticed that learning almost any high-level framework was (larger than i expected) sunken effort. nothing gained beyond possibly a faster start to getting something up
[19:38:49] <StephenLynx> if the framework has a vulnerability, you're screwed.
[19:39:04] <synthmeat> yeah, once those dropped socket.io connections start to acumulate, you're hosed
[19:43:39] <synthmeat> (that was pre 1.0 socket.io issue, prolly fixed now)
[19:44:05] <StephenLynx> never touched that either.
[19:44:17] <StephenLynx> not only frameworks, but I don't use do-all libs.
[19:44:39] <StephenLynx> I once used websockets by using just a websocket library.
[19:46:21] <StephenLynx> at first I tried not using a lib but the assholes made websockets such a convoluted protocol that I gave up on doing it from scratch.
[19:46:34] <StephenLynx> it gets to the point it uses a "magical string" for the handshake.
[22:00:01] <lacour> In production with Mongoid and MongoDB Atlas, I'm noticing some random fields being corrupted with ObjectIDs that are entirely nonsensical (i.e. with timestamps that are far in the past or future, one is for 2028). The documents don't have any ObjectIDs beyond _id, and the app itself doesn't handle/create any. Any ideas?
[22:01:53] <cheeser> you'll want to post to mongo-user with that one. neither emily nor durran lurk here.