Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Sorry if this is somewhat off-topic, but I'm not sure where else to ask this.

I'm working on a site that involves users posting formatted text documents. They'll actually be using POD with a different L<> syntax for the formatting--it's simple, safe (with =begin/=end/=for disabled), and does what's needed. The structure of the site is something like an Everything Engine Lite--not everything's a node, but it's extremely database-driven.

At this point, I don't know how how heavy the load will be, but it could potentially be very popular, so I'm trying to make sure it can handle significant loads. To that end, I'm parsing the POD only once (when a document is posted) and storing the HTML version for later.

My question is, will it be more efficient to store the HTML versions of these POD documents in the database or in a separate file? (Realize that if it's on-disk, I can read it in line-by-line, whereas I believe keeping it in-database would essentially mean slurping everything into memory.) These documents will probably range between 2-100KB; I can probably cap them at 65K (the size of a MySQL TEXT column).

Thanks in advance for any advice.

=cut
--Brent Dax
There is no sig.


In reply to Large chunks of text: in-database or in-filesystem? by BrentDax

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (5)
As of 2022-05-22 20:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you prefer to work remotely?



    Results (81 votes). Check out past polls.

    Notices?