FreePgs.com Forum
September 22, 2021, 03:42:46 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Click Here for Toll-Free Service for your business starting at $2.00 per month and 4.5 cents per minute
 
   Home   Help Search Login Register  
Pages: 1 ... 8 9 [10]
 91 
 on: September 18, 2014, 11:42:44 PM 
Started by admin - Last post by Scorpion Illuminati
I applied for migration via help desk, but i cannot access the ticket anymore because I tried to upgrade my help desk account to a full account. As a result I am as of this post am still waiting for the validation email which until i receive and click on the link won't let me log in. The helpdesk username is the same as my panel username. Any assistance would be greatly appreciated.

Sincerely,

Aleeious

I have forced your Helpdesk account as validated.
Sorry I'm still getting the error:
Quote
Sorry, you must validate your account by clicking the link you received in our email to you. If you did not receive and email, click here.

Please go back and try again. If the problem persists, please contact an administrator.
Any assistance would be greatly appreciated.

Sincerely,

Aleeious

 92 
 on: September 18, 2014, 11:19:40 PM 
Started by admin - Last post by admin
I applied for migration via help desk, but i cannot access the ticket anymore because I tried to upgrade my help desk account to a full account. As a result I am as of this post am still waiting for the validation email which until i receive and click on the link won't let me log in. The helpdesk username is the same as my panel username. Any assistance would be greatly appreciated.

Sincerely,

Aleeious

I have forced your Helpdesk account as validated.

 93 
 on: September 18, 2014, 11:15:45 PM 
Started by admin - Last post by Scorpion Illuminati
I applied for migration via help desk, but i cannot access the ticket anymore because I tried to upgrade my help desk account to a full account. As a result I am as of this post am still waiting for the validation email which until i receive and click on the link won't let me log in. The helpdesk username is the same as my panel username. Any assistance would be greatly appreciated.

Sincerely,

Aleeious

 94 
 on: September 02, 2014, 10:06:22 PM 
Started by admin - Last post by admin
We are testing a new cPanel server at the NYC data center.

If anyone would like to be moved to this server, please let us know by sending a message via the Helpdesk.

This server is running CloudLinux so it allows various PHP versions to be selected, modules to be included/excluded, PHP settings changed, etc.

If you are on EAST, this server should provide more performance as it is SSD based.

 95 
 on: August 16, 2014, 12:27:55 AM 
Started by admin - Last post by admin
Reminder: PHP 5.2 and 5.3 are slated to be removed from this system once 5.6 goes to release.

PHP 5.3 is now officially EOL'd, so no more security updates are coming to it.

 96 
 on: August 12, 2014, 10:49:48 PM 
Started by admin - Last post by admin
...My app uses where clauses for user.username, username.password, matchindex.id, matchindex.challenger and matchindex.defender. You can see how everything works on my github page. Any assistance would be greatly appreciated....

As long as the fields you have listed are indexed along with any fields used in your JOIN statements, you will be fine.

 97 
 on: August 11, 2014, 11:14:22 PM 
Started by admin - Last post by Scorpion Illuminati
As long as your site isn't taking multiple seconds per page load, you are generally fine.  (We are not talking about time waiting on downloading files to the client computer, Nginx offloads that part from Apache very well, but time waiting on your pages to generate due to waiting for MySQL, waiting for a remote API, etc.)

For the most part, we try to keep the load low on the servers.  We let users exceed CPU-I/O time limits for a period of time in case they are working with their site or are getting a traffic spike.  When we get complaints on the performance of a specific server, if we find these high resource users and the reason they are using resources is Google is crawling their site (because their site takes 10 seconds to load on each pageview), we generally disable the user and attempt to help them index their tables or explain what processes are using too many resources.

If your site loads fast, you will likely never fall into this group.

By replying to this topic, we didn't want to send the message that we were thinking of discontinuing the service, because we are not.  We may need to consolidate it further in an effort to lose less money, but there is no reason the service will need to be discontinued in the near future.
I'm sorry but everytime i see:
Quote from: admin
I guess our only choice will be to shut this down.
I start to fear the worst.

Quote from: admin
You should create indexes for any column your are sorting or filtering by.  If you are not sorting by that column (i.e. using it in an ORDER BY clause) or filtering by that field (using it in a WHERE clause), this will not be necessary.  [This should also be done if joining tables using these fields.]
My app uses where clauses for user.username, username.password, matchindex.id, matchindex.challenger and matchindex.defender. You can see how everything works on my github page. Any assistance would be greatly appreciated.

Sincerely,

Aleeious

 98 
 on: August 10, 2014, 08:29:55 PM 
Started by admin - Last post by admin
As long as your site isn't taking multiple seconds per page load, you are generally fine.  (We are not talking about time waiting on downloading files to the client computer, Nginx offloads that part from Apache very well, but time waiting on your pages to generate due to waiting for MySQL, waiting for a remote API, etc.)

For the most part, we try to keep the load low on the servers.  We let users exceed CPU-I/O time limits for a period of time in case they are working with their site or are getting a traffic spike.  When we get complaints on the performance of a specific server, if we find these high resource users and the reason they are using resources is Google is crawling their site (because their site takes 10 seconds to load on each pageview), we generally disable the user and attempt to help them index their tables or explain what processes are using too many resources.

If your site loads fast, you will likely never fall into this group.

By replying to this topic, we didn't want to send the message that we were thinking of discontinuing the service, because we are not.  We may need to consolidate it further in an effort to lose less money, but there is no reason the service will need to be discontinued in the near future.

 99 
 on: August 10, 2014, 08:17:05 PM 
Started by admin - Last post by admin
I feel bad for the users that don't cause problems, but unfortunately, there are numerous problems being caused, most are not intentional (while some are).

-Dormant sites/scripts that then get exploited (because they are not kept up to date)
-Users using too many resources (page loads taking 10+ seconds, easily DoS'd)
-Improperly indexed tables (likely no indexes at all on some)
-Inefficient database queries
-Selection of lower PHP versions that is necessary to run their script.
So do i, a few bad apples ruining it for everyone is very unfair.
Quote
For tables: If a field is in the ORDER BY or WHERE clauses, be sure those fields are indexed.  (i.e. If you are filtering for something and/or sorting by something, those fields you are sorting and filtering by should be indexed at the very minimum.)
Could you please explain this a bit more? Does that mean I should create indexes for all my columns? Any assistance would be greatly appreciated.

Sincerely,

Aleeious

You should create indexes for any column your are sorting or filtering by.  If you are not sorting by that column (i.e. using it in an ORDER BY clause) or filtering by that field (using it in a WHERE clause), this will not be necessary.  [This should also be done if joining tables using these fields.]

 100 
 on: August 06, 2014, 04:52:29 PM 
Started by admin - Last post by Scorpion Illuminati
I feel bad for the users that don't cause problems, but unfortunately, there are numerous problems being caused, most are not intentional (while some are).

-Dormant sites/scripts that then get exploited (because they are not kept up to date)
-Users using too many resources (page loads taking 10+ seconds, easily DoS'd)
-Improperly indexed tables (likely no indexes at all on some)
-Inefficient database queries
-Selection of lower PHP versions that is necessary to run their script.
So do i, a few bad apples ruining it for everyone is very unfair.
Quote
For tables: If a field is in the ORDER BY or WHERE clauses, be sure those fields are indexed.  (i.e. If you are filtering for something and/or sorting by something, those fields you are sorting and filtering by should be indexed at the very minimum.)
Could you please explain this a bit more? Does that mean I should create indexes for all my columns? Any assistance would be greatly appreciated.

Sincerely,

Aleeious

Pages: 1 ... 8 9 [10]
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!