#dev | Logs for 2021-01-03

« return
[02:07:32] <Bytram> Seem to have been having some hiccups on the site; *looked like* css errors; confirmed with other users (see #soylent); just bounced the servers
[02:08:19] * Bytram did not notice anything obvious in the apache error log on fluorine
[02:09:26] <Bytram> by obvious, I mean spitting out an error every 2-5 seconds like we saw when the Most Recent Journal Entries block disappeared
[12:57:38] <Bytram> TheMightyBuzzard: I'm curious, what table changes are you making?
[12:58:17] <TheMightyBuzzard> well, for starters, story notes need to be TEXT not VARCHAR
[12:59:51] <Bytram> if it's not too late, I'd lurv to have a larger User Space
[13:00:16] <Bytram> (Slashbox on RHS of the main page)
[13:01:28] <Bytram> Hmm, there were some ad hoc template changes I'd made that are not in the DB...
[13:02:22] <Bytram> e.g. [Skip to Comments] link at the top of a story.
[13:03:40] <TheMightyBuzzard> what's a rhs
[13:04:01] <requerdanos> it's across from the lhs
[13:05:39] <Bytram> requerdanos++ =)
[13:05:39] <Bender> karma - requerdanos: 1
[13:06:01] <Bytram> Left Hand Side vs Right Hand Side
[13:07:05] <TheMightyBuzzard> oh, you can tweak that with Stylish or some such.
[13:07:15] <TheMightyBuzzard> not viable for it to be a user setting
[13:07:49] <Bytram> try again. the DB limits how much text can be stored there.
[13:07:52] <Bytram> IIRC
[13:08:58] <TheMightyBuzzard> huh?
[13:09:07] <TheMightyBuzzard> thought you were talking about width
[13:09:21] <Bytram> width of the field in the DB
[13:09:38] <TheMightyBuzzard> nothing in the slashboxes is directly in the db
[13:09:58] <TheMightyBuzzard> programatically generated
[13:11:09] <Bytram> Yes, but drawing on info from the DB...
[13:12:16] <Bytram> I can't reference the page right now, of course, but there is a user setting where I can store stuff to be displayed in the user info box, AFAICT it's limited to 255 char
[13:12:35] <TheMightyBuzzard> Ooooooh, your own personal slashbox.
[13:12:44] <Bytram> nod nod
[13:13:26] <TheMightyBuzzard> can't expand that to TEXT without placing a limit in the code or folks could upload a whole drive full of text.
[13:14:09] <Bytram> varchar(1024) ?
[13:15:20] <TheMightyBuzzard> naw, varchars stay in ram
[13:16:39] <Bytram> okaaay, but does every varchar(256) actually take up 256? o/w why not just call it a char(256)?
[13:17:22] <TheMightyBuzzard> we pretty much never optimize our db, so, yeah, they do
[13:17:44] <Bytram> ohhh, huh.
[13:18:15] * Bytram scratches his head
[13:18:32] <Bytram> why not?
[13:18:54] <Bytram> Less ram pressure sounds like it would be a good thing.
[13:19:41] <TheMightyBuzzard> load on the db while we optimize
[13:20:20] <requerdanos> of course, designing the schema to not need runtime optimization is itself an optimization
[13:20:20] <Bytram> can't <tt>nice</tt> it?
[13:21:42] <TheMightyBuzzard> it's not a separate process, it's the db process
[13:21:43] <Bytram> so, conceptually, like doing garbage collection? Clean as you go... or wait and do it all in one big crunch.
[13:21:53] <Bytram> ??
[13:22:33] * Bytram is in no way criticizing -- finding this fascinating
[13:22:36] <TheMightyBuzzard> nice applies to processes. if you're altering the db, the db process is going to peg out.
[13:22:56] <TheMightyBuzzard> same db process that serves up info
[13:23:09] <TheMightyBuzzard> okay, time for DROP TABLE soylentnews;
[13:23:23] <TheMightyBuzzard> scuse me, DROP DATABASE soylentnews;
[13:24:10] <TheMightyBuzzard> may take a minute or two
[13:24:17] <Bytram> and, given multiple things to do, the DB has no prioriticization? It gets a task and just hauls off and does it?
[13:24:19] <TheMightyBuzzard> oh, nope, that was pretty fast
[13:25:19] <TheMightyBuzzard> now to fill it back up
[13:25:42] <Bytram> Even a simple OS has a scheduler and a dispatcher as well as different priorities for different tasks. Find it had to understand that a DB has nothing along those lines.
[13:26:09] <TheMightyBuzzard> might, dunno
[13:26:19] <Bytram> fair 'nuf
[13:26:36] <TheMightyBuzzard> still slows things down if you're trying to alter a cell of data and read it with another call at the same time
[13:27:15] <Bytram> collisions, aye.
[13:28:20] <TheMightyBuzzard> think i'll run grab me a smoke while the restore from backup runs. going to be a while.
[13:28:36] <Bytram> locks, mutexes, and their ilk... that's some really fun ju-ju on a multi-tasking multi-processing system
[13:28:40] <Bytram> k
[13:28:49] * TheMightyBuzzard altered the backup for notes to be TEXT, saves time
[13:29:15] * Bytram appreciates the pointers
[13:30:07] <Bytram> break time; biab
[13:36:18] <Bytram> Oh! Please please please please! When I add a delete reason for a story submission and then click the delete button, can you make it automatically save the delete reason at the end of the story note? Waste so much time having to manually enter the delete reason in the story notes field, click update, re-open the submission, copy reason from notes field. paste into delete reason field, and then click delete button..
[13:36:46] <Bytram> break time for me too, biab ~ 1/2 hr or so
[13:57:23] <TheMightyBuzzard> Bytram, not while i'm doing db maintenance. that's a code thing.
[14:55:54] <chromas> bump up the title length limit too while you're at it :)