Going to the page with just code is pretty fast in PM. That makes sense since the server doesn't need to do a lot. But when it takes 30+ seconds for an intermediate page to render, I tend not to be bothering as well. Which is a shame.

In my view, the intermediate page is waisting server resources, as it does not really bring anything new, apart from the link to the code download. If the link would be directly available, it would save on the server side as well as on the client side. And as far as I understand, no extra database access would be needed to create the link. So it would only be a little bit more CPU and some more HTML output.

I have no idea whether the slowness of PM is caused by CPU or (database) IO starvation. If it's IO starvation, then some extra CPU would not be a problem.

What then remains is the question whether the extra bandwidth needed for the extra HTML compares to the bandwidth saved by the extra page not having to be sent. Looking at the amount of whitespace in the HTML sent by PM, and the fact that it does not seem to support gzip encoding, leads me to conclude that the possible extra bandwidth should not be a problem either.

Liz

---

---

• 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.