Forum Search Tool?
- Thread starter Rikket_The_Rogue
- Start date
Rikket_The_Rogue
Grandmaster
I mainly use google chrome; it's my go to. Shortbus was suggesting I try it to see if it was isolated to one program.
Rikket_The_Rogue
Grandmaster
I suppose if I received a page from a admin with a expressed list of grievances I could review, I could change to accommodate.
However that hasn't been forth coming, and silence doesn't tell me much; I never received a warning about abusing the search bar. And after being DDoS'ed for a month it's kind of ironic that staff would do the same thing to a player based on.... what, exactly? You mentioned being a douche, but what exactly are we talking about here?
I've made no racist, or sexist comments.
I've accused no one of federal crimes.
I haven't made millions of threads titled, 'LAWL $$$ WINS AGAIN' or 'EQMS ARE LOOSERS' or 'EQMS IS THE BEST'.
So what exactly have I done, admin?
However that hasn't been forth coming, and silence doesn't tell me much; I never received a warning about abusing the search bar. And after being DDoS'ed for a month it's kind of ironic that staff would do the same thing to a player based on.... what, exactly? You mentioned being a douche, but what exactly are we talking about here?
I've made no racist, or sexist comments.
I've accused no one of federal crimes.
I haven't made millions of threads titled, 'LAWL $$$ WINS AGAIN' or 'EQMS ARE LOOSERS' or 'EQMS IS THE BEST'.
So what exactly have I done, admin?
ratpie
Novice
its your browser, try firefox or delete chrome then go to your computers setting and delete all chrome folders and retry this happend to my on a few forums also.
Rikket_The_Rogue
Grandmaster
It's not my browser; IE and Fire Fox are both effected as well.
Page Inspection tool showed that the TTFB (time to first bit) is an average of about 18 seconds.
Basically I send a HTTP request when I click a link, and the site responds, but in this case 18 seconds later.
Looking up the causes all point to the server-side. With anything from jumbled protocol, to over-traffic which is why I thought the site was still being DDoS'd
Slow Server Performance Factors
Once you know you've got a server performance issue, how do you know what to fix? Here are some server performance issues that may be slowing down your server.
Memory leaks
Leaks can accumulate maxing out the memory of your server and slowing it to a crawl. Solution: You can of course increase the memory in your server, but the best fix would be to locate the memory leak and recode the offending script.
Too many processes / connections
Programs that keep spawning processes or don't release server connections can bog down your server response time. Solution: rewrite the code to release resources upon completion.
External resource delays
Loading JavaScript or other resources from off-site can cause indeterminate delays for your own site. JQuery, advertising scripts, Google Plus One, Facebook, and other external resources are typically loaded with a remote JavaScript call to Google, Facebook, or some other busy site. Loading infrequently changing resources (like a programming library) remotely introduces DNS and network overhead, and indeterminate delay from a server you don't control. Solution: Periodically cache the resource locally on your server and serve locally. Use a CRON script to copy the resource.
Inefficient SQL Queries
Database queries that are written poorly can cause slowdowns to web sites. Databases that aren't indexed properly can also cause slowdowns.
Slow database calls
Each additional plugin can make calls to a database, which can add up. Solution: Disable any unnecessary plugins in Wordress or your favorite CMS.
Insuficient server resources
Low memory, bandwidth caps, or limited disk space can cause paging and poor server response times. Solution: Use VMStat, Top, etc. to locate bottlenecks and either decrease resource usage or increase resources (more memory and disk space can't hurt).
Overloaded Shared Servers
Some hosting companies put too many sites on the same shared server. Servers have limited resources and these can be taxed (memory, processes, bandwidth, etc.) by having too many sites competing for the same resources. Just one heavily loaded site hosted on a shared server can slow down all the other sites hosted there (Our own WebPageAnalyzer.com was kicked off a shared server for that reason). Solution: Move to a lightly loaded shared server, or a dedicated server where you have complete control. .
Inconsistent website response times
If your site is slower during different parts of the day (say near lunch time for example), it may be due to increased load on the server slowing down your response time due to maxed out resources (processes, memory, disk space, bandwidth). Solution: Find which resource(s) are highly utilized (CPU, memory, processes etc) during high load and profile and fix "hot code" to help minimize the impact of your scripts. Increasing the resources allocated to your server may help (number of processes for example). A dedicated server may also help here.
http://www.websiteoptimization.com/speed/tweak/time-to-first-byte/ - Knowledge source.
Considering there are staff members trolling I'd say it's done on purpose, but I have no proof of that.
That being said, just because it's not done on purpose doesn't mean it's not the server-side communication; it definitely is.
Page Inspection tool showed that the TTFB (time to first bit) is an average of about 18 seconds.
Basically I send a HTTP request when I click a link, and the site responds, but in this case 18 seconds later.
Looking up the causes all point to the server-side. With anything from jumbled protocol, to over-traffic which is why I thought the site was still being DDoS'd
Slow Server Performance Factors
Once you know you've got a server performance issue, how do you know what to fix? Here are some server performance issues that may be slowing down your server.
Memory leaks
Leaks can accumulate maxing out the memory of your server and slowing it to a crawl. Solution: You can of course increase the memory in your server, but the best fix would be to locate the memory leak and recode the offending script.
Too many processes / connections
Programs that keep spawning processes or don't release server connections can bog down your server response time. Solution: rewrite the code to release resources upon completion.
External resource delays
Loading JavaScript or other resources from off-site can cause indeterminate delays for your own site. JQuery, advertising scripts, Google Plus One, Facebook, and other external resources are typically loaded with a remote JavaScript call to Google, Facebook, or some other busy site. Loading infrequently changing resources (like a programming library) remotely introduces DNS and network overhead, and indeterminate delay from a server you don't control. Solution: Periodically cache the resource locally on your server and serve locally. Use a CRON script to copy the resource.
Inefficient SQL Queries
Database queries that are written poorly can cause slowdowns to web sites. Databases that aren't indexed properly can also cause slowdowns.
Slow database calls
Each additional plugin can make calls to a database, which can add up. Solution: Disable any unnecessary plugins in Wordress or your favorite CMS.
Insuficient server resources
Low memory, bandwidth caps, or limited disk space can cause paging and poor server response times. Solution: Use VMStat, Top, etc. to locate bottlenecks and either decrease resource usage or increase resources (more memory and disk space can't hurt).
Overloaded Shared Servers
Some hosting companies put too many sites on the same shared server. Servers have limited resources and these can be taxed (memory, processes, bandwidth, etc.) by having too many sites competing for the same resources. Just one heavily loaded site hosted on a shared server can slow down all the other sites hosted there (Our own WebPageAnalyzer.com was kicked off a shared server for that reason). Solution: Move to a lightly loaded shared server, or a dedicated server where you have complete control. .
Inconsistent website response times
If your site is slower during different parts of the day (say near lunch time for example), it may be due to increased load on the server slowing down your response time due to maxed out resources (processes, memory, disk space, bandwidth). Solution: Find which resource(s) are highly utilized (CPU, memory, processes etc) during high load and profile and fix "hot code" to help minimize the impact of your scripts. Increasing the resources allocated to your server may help (number of processes for example). A dedicated server may also help here.
http://www.websiteoptimization.com/speed/tweak/time-to-first-byte/ - Knowledge source.
Considering there are staff members trolling I'd say it's done on purpose, but I have no proof of that.
That being said, just because it's not done on purpose doesn't mean it's not the server-side communication; it definitely is.
The Gandin
Grandmaster
Maybe condense your novel of a sig to: "EQMS is bad, mmkay."
Rikket_The_Rogue
Grandmaster
Having a large sig isn't a forum rule.
As far as I can tell there isn't even a character limit.
As far as I can tell there isn't even a character limit.
The Gandin
Grandmaster
[e shush
