# Long sig lines **URL:** \ **Category:** About This Message Board\ **Created:** [April 9, 2001, 4:07am UTC](https://boards.straightdope.com/t/long-sig-lines/61317 "2001-04-09T04:07:55Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![pantom](https://avatars.discourse-cdn.com/v4/letter/p/34f0e0/32.png) [@pantom](https://boards.straightdope.com/u/pantom)\ **Post date:** [April 9, 2001, 4:07am UTC](https://boards.straightdope.com/t/long-sig-lines/61317/1 "2001-04-09T04:07:55Z")
I noticed when I changed my sig a month ago or so that it changed on even my old posts, which means that every time you open a page the software has to go out to each person’s profile to get their sigs, if they have one. This is odd. Why isn’t the sig saved with the post? This would certainly make things faster, I would think. ---
**Author:** ![waterj2](https://avatars.discourse-cdn.com/v4/letter/w/858c86/32.png) [@waterj2](https://boards.straightdope.com/u/waterj2)\ **Post date:** [April 9, 2001, 6:55am UTC](https://boards.straightdope.com/t/long-sig-lines/61317/2 "2001-04-09T06:55:05Z")
I doubt it. It has to look in both places anyways, so I’d imagine the time to be about the same. Storing one sig per user takes less space than storing the equivalent amount of text with each post, thus saving hard drive space. ---
**Author:** ![Pot\_o\_Gold](https://avatars.discourse-cdn.com/v4/letter/p/3e96dc/32.png) [@Pot\_o\_Gold](https://boards.straightdope.com/u/Pot_o_Gold)\ **Post date:** [April 9, 2001, 3:45pm UTC](https://boards.straightdope.com/t/long-sig-lines/61317/3 "2001-04-09T15:45:00Z")
The page is made of hundreds of such file references. Every little icon, every post is separate as well. ---
**Author:** ![Jet\_Jaguar](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/jet_jaguar/32/3562_2.png) [@Jet\_Jaguar](https://boards.straightdope.com/u/Jet_Jaguar)\ **Post date:** [April 9, 2001, 3:59pm UTC](https://boards.straightdope.com/t/long-sig-lines/61317/4 "2001-04-09T15:59:29Z")
> [@](#): > > \*Originally posted by pantom \* > **Why isn’t the sig saved with the post?** My guess is that it’s done this way to save disk space. The sig only has to be stored once in each user’s profile, and only a signature flag needs to be stored with the message itself. ---
**Author:** ![pantom](https://avatars.discourse-cdn.com/v4/letter/p/34f0e0/32.png) [@pantom](https://boards.straightdope.com/u/pantom)\ **Post date:** [April 10, 2001, 2:03am UTC](https://boards.straightdope.com/t/long-sig-lines/61317/5 "2001-04-10T02:03:43Z")
The hard drive space argument is good, but if the sigs are getting to be a problem, it might be time to consider saving them. Disk space is cheap, getting cheaper all the time. And drive speed keeps going up too. ---
**Author:** ![friedo](https://avatars.discourse-cdn.com/v4/letter/f/8edcca/32.png) [@friedo](https://boards.straightdope.com/u/friedo)\ **Post date:** [April 10, 2001, 6:54am UTC](https://boards.straightdope.com/t/long-sig-lines/61317/6 "2001-04-10T06:54:56Z")
Remember that this board operates from a relational datbase (MySQL, specifically) and people who design relational database implimentations abhor database redundancy. This is the way the software is written, and I doubt the SDMB Admins want to go poking around to change it; it would be non-trivial. As an aside, allow me to make up some numbers. Let’s say the average sig is 100 bytes long. There are currently some 66,000 threads, and let’s assume the average thread has 10 posts. Let us further assume that 75% of those posts have sigs attached. That works out to: 66,000 x 10 = 660,000 posts total 660,000 x .75 = 495,000 posts with sigs 495,000 x 100 = 495,000,000 bytes worth of sig, or a little less than 495 megabytes, just for sigs! That’s the advantage of the relational model. Takes more time, but the space saved is enourmous. ---
**Author:** ![friedo](https://avatars.discourse-cdn.com/v4/letter/f/8edcca/32.png) [@friedo](https://boards.straightdope.com/u/friedo)\ **Post date:** [April 10, 2001, 6:58am UTC](https://boards.straightdope.com/t/long-sig-lines/61317/7 "2001-04-10T06:58:48Z")
Doh. I should make it clear that the above demonstrates why it is not a good idea to attach the sig in every single post. Seeing as we have 13,000 members, each having a 100 byte sig (but not all members have sigs, but I’ll pretend they do to make my point) that’s only 1,300,000 bytes, slightly over one megabyte to store the sigs, instead of half a gigabyte. ---
**Author:** ![Redboss](https://avatars.discourse-cdn.com/v4/letter/r/8baadc/32.png) [@Redboss](https://boards.straightdope.com/u/Redboss)\ **Post date:** [April 10, 2001, 9:20am UTC](https://boards.straightdope.com/t/long-sig-lines/61317/8 "2001-04-10T09:20:10Z")
Just say no to sigs! Eschew 'em! ---
**Author:** ![SPOOFE](https://avatars.discourse-cdn.com/v4/letter/s/c5a1d2/32.png) [@SPOOFE](https://boards.straightdope.com/u/SPOOFE)\ **Post date:** [April 10, 2001, 11:03am UTC](https://boards.straightdope.com/t/long-sig-lines/61317/9 "2001-04-10T11:03:23Z")
> [@](#): > > 495,000 x 100 = 495,000,000 bytes worth of sig, or a little less than 495 megabytes, just for sigs! You know, 495 megabytes is hardly a lot of memory for a server. Consider: Only a tiny fraction of that would be summoned up at a time, and the amount itself must be trivial in relation to the total memory used up by all the posts on the board. The problem isn’t hard drive usage but BANDWIDTH usage… having a few thousand or so threads being loaded up at a time will stress the server, NOT the content is being loaded up. The only long-term solution is a new server… which probably isn’t going to happen any time soon.