I checked with my hosting service (bluehost). They are having a hardware issue. An admin is onsite right now fixing it.<br clear="all"><br><br>Shawn T Perry<br>Red Mop Computing Services<br>email: <a href="mailto:shawn@redmop.com" target="_blank">shawn@redmop.com</a><br>
office: 720-319-7627<br>cell: 303-881-2623<br>web: <a href="http://www.redmop.com/" target="_blank">http://www.redmop.com</a><br>
facebook: <a href="http://www.facebook.com/pages/Red-Mop-Computing-Services/114352628589778" target="_blank">http://www.facebook.com/pages/Red-Mop-Computing-Services/114352628589778</a><br>linkedin: <a href="http://www.linkedin.com/in/shawnperry" target="_blank">http://www.linkedin.com/in/shawnperry</a><br>
<br><br><div class="gmail_quote">On Tue, Jun 7, 2011 at 1:08 PM, Lorin Ricker <span dir="ltr"><<a href="mailto:Lorin@rickernet.us">Lorin@rickernet.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I hammered & clicked on the new site from about 12:50 to 1:00pm --<br>
Noticed that it "felt" a bit slower than my first attempts late last<br>
night (at around 10:30pm), but certainly within my own tolerance...<br>
pages were loading within 1-to-2 seconds easily.<br>
<br>
I also note that my own email ISP (Godaddy) is timing out SMTP when I'm<br>
sending/replying to emails right now -- including this very message --<br>
so we could be seeing some overall regional network congestion during<br>
this testing period in question.<br>
<br>
Don't be too fast to throw this baby out with its bathwater... there's a<br>
lot of fine work & effort that have gone into this Drupal-based website<br>
facelift, and I think that it's worth investing in for the next while to<br>
make it work well and keep it working as a CLUE/Denver resource.<br>
<br>
Again, thanks to all who've contributed time & treasure so far!<br>
best regards,<br>
<font color="#888888"> -- Lorin<br>
</font><div><div></div><div class="h5"><br>
On 06/06/2011 10:57 PM, David L. Willson wrote:<br>
> Please try to load up the website tomorrow from noon to 1PM. Use a<br>
> script if you like, or just your clicking fingers.<br>
><br>
> Shawn will probably be able to monitor the serverat that time, and<br>
> this should generate about as much simultaneous traffic as we might<br>
> reasonably expect anytime soon.<br>
><br>
> If it survives that hit, and stays up for a week afterward, it's<br>
> almost certainly reliable enough for our purposes.<br>
><br>
> I'd like to ask, and this is a new request, that we don't cut in the<br>
> new DNS record until daily backups have succeeded for three days<br>
> without administrative assistance, and at least three people known to<br>
> the list have enough access to the server to take care of business if<br>
> things go to Heck. (Shawn, Dennis, and Dave A, perhaps?)<br>
> _______________________________________________ clue mailing list:<br>
> <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a> For information, account preferences, or to<br>
> unsubscribe see: <a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</div></div></blockquote></div><br>