As the server will have to dynamically render each page anyhow (barring any cache-ing issues -- and those will be the same for a read/write as for a read-only site), adding the few links which allow you to go to a page where you can enter your comments, would not really make a difference.

The speed (or perceived lack of it) has nothing to do with the fact that we can write comments.

If you never write a comment, you will not experience any delays in your comments being accepted, but the rendering of the pages will be as "fast" (not faster) as for anyone.

Now if there was a separate server that only serves pages to those who are not interested to make comments, there is a chance that it might be faster, but only due to the fact that that server would be less used and thus the load on the server --by definition-- will be less. But if you are adding another server anyhow, why not make it a full read/write site also? If you divide the load over more servers, you get better response in any case.

---

---

• 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 How to display code and escape characters are good places to start.