Lot of duplicate posting

We are aware of the issue and tech ops is working on it. Thanks for the post.

still slow....

Yeah, we're still working on a few things to get it back to normal. I'm thinking there will be more information to come.

i am stuck on one mutual profile. help!!!:

And i had actually blamed my phone for it...

blcollar, please email me (do not post it here) the exact user name or the URL to the profile. What you're seeing is likely like a known bug, but I can double check.

Seems to hit slow for me around midnightish or so Mountain Time, pretty common for the site to be relatively slow throughout the early morning hours...Every rare once in awhile during the day before midnight it can go slow, but mainly after midnight.

Kind of feels like the server throttles down or something at night.

Update: Hanging during the day, still loads just takes a rather long time...No 404 or any error, just slow. Been happening quite frequently throughout the day for the last two days, 11ish in the afternoon here and hitting spikes.

seems to me all the ads are slowing it down... seems ok today tho... good work guys

Thanks for the feedback, guys. We are making adjustments to the site in order to maximize performance, so this input might be useful.

Is it also a reason why i cannot open a page/s,, it goes more often?

9:30ish and the site damn near died, been loading three pages for the last five or so minutes.

Denver area if that helps, loaded fine just now...But literally dead for the last five or so.

Instances of sluggishness should go down, as we've upgraded our DB server:
http://mingle2.com/topic/show/353396

Charles,


These are the header fields from the mingle2 server

null : HTTP/1.1 200 OK
Server : nginx/0.6.32
Date : Thu, 02 May 2013 03:11:06 GMT
Content-Type : text/html; charset=utf-8
Content-Length : 37078
Set-Cookie : _session_id=18071163e2049b0b25be4b06465f3e86; domain=.mingle2.com; path=/
Status : 200 OK
P3P : CP="NOI DSP COR NID ADMa OPTa OUR NOR"
X-Runtime : 0.05494
ETag : "b257553a40dcb3d37a9fab349c94d4ff"
Connection : Close
Cache-Control : private, max-age=0, must-revalidate
http://www.mingle2.com

This is the information the server reports back to client browsers each time a request is made, minus one cookie (when the request line is http://www.mingle2.com only).


I noticed you said you had new server software; but also that the server remained the same nginx (could have been slightly different I only looked at it a couple times).


This property could possible be new and I do not remember seeing it before

X-Runtime : 0.05494

Which is about exactly as long as it may take a server to respond to the request after it is received. Which is about 55 milliseconds (there is a thousand in a full second) not likely to notice a huge difference even if you cut this number in half, because the real thing that takes up the time is the transmission across the wires from the client to the server and from the server back to the client. It takes a few seconds as opposed to a fraction of a second that the server takes to prepare the file or stream for transmission ( .055 which is far less then a split second ).

Next,
If you want to cut back the transmission time.. you may want to consider these headers

Content-Type : text/html; charset=utf-8
Content-Length : 37078

Content type text/html is the MIME type for markup language. Unlike what I said before this is not necessarily compressed gzip ( with broadband transmitting a content length of 37078 bytes which is about 36 Kilobytes , not hugely noticeable but will take a little bit of time off the transmission ). Larger sized pages will load quicker and be human detectable.

Try my servlet when I was practicing gzip.

http://192.168.1.3/CoreServlets/CompressionGZip

It is a 12 mb file and takes about as long as a regular file on a slow connection to load.

Heres a copy of my headers from my Opera browser

Name Value
user-agent Opera/9.80 (Windows NT 5.1) Presto/2.12.388 Version/12.12
host localhost
accept text/html, application/xml;q=0.9, application/xhtml+xml, image/png, image/webp, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1
accept-language en-US,en;q=0.9
accept-encoding gzip, deflate
cookie tyesha=yes; JSESSIONID=F7D869850865D723B51DE075E8C3A0B1
connection Keep-Alive

Notice accept-encoding gzip, deflate.. you can read the headers from your browser right here

http://192.168.1.3/CoreServlets/ReadRequestHeaders

Almost all browsers deflate gzip compression.. also in the Cache control property of the mingle server is this Cache-Control : private, max-age=0, must-revalidate.. max age 0 means it will delete the copy as soon as it is created... not very knowledgeable on cached copies of documents though.... mingle2 is ever changing .. new posts to different forums which is probably why you do not use it.. the browsers checks when documents were last modified and it pertains to this little scenario..where cached documents come into effect... I would not know I do not use them intentionally from my server at home.

In the off chance you went too look at the site my server was down yesterday due to an Internet outage.... It is a regular satallite ISP.. but it is up and running again .. thank god... the poinht is the links should work now...

I have passed along your information, Mirage4279, in case tech ops needs it.

The super duper server seems to be the same ol' same ol'.

Mine always seems to work fine. Road Runner is always fast. I assumed double posts were from mobile devices as well

We're not seeing any performance issues today, but we'll be extra vigilant, just in case.