Jump to content

hbarnetworks

Members
  • Posts

    109
  • Joined

  • Days Won

    14

Posts posted by hbarnetworks

  1. HSTS just requires all your internal and external links to be HTTPS there is no specific requirement. If you fail even 1 link your page will not load. That is HSTS. 

    Not sure what you mean by firewalling, but Iptables is plenty just open port 443 that is all KVS requires. If you need remote access open SSH on a different port and enable Fail2Ban.

  2. Let me tell you this.

    What does your site bring to the table that litterly millions of other sites dont? Thats what google looks at. Do you have a specific model thats scarce on other sites but alot heavy on your site than thats your lifeline keyword. You are not gonna rank on mainstream keywords. If you only focus on mainstream keywords than you will never get traffic, thats useless SEO the biggest networks have already claimed those.

    • Like 3
    • Thanks 2
  3. 1 hour ago, Scumtron said:

    There is no point in doing this. Yes you then have a replica but thats all it is. Nothing will be read from this server. You cant simply do a round robin either using dns because this will cause data mismatching in the databases.

    best bet is to get atleast 3 MySQL (3 is minimum for galera) activate-galera (comes preinstalled with the latest mariadb). Make only 1 of the servers writeable this is easily done use proxySQL and then use proxySQL as the main SQL connection to do the loadbalancing. 

    Setup like this can easily be googled on how to do it.

     

    FYI: this does require to set your database engine to INNODB. kvs uses MyISAM by default.

  4. Sort indexes barely use any IO. it seems the problem is that either your storage solution just sucks. Or your you SQL config lacks memory to process the queries in memory. Either get SSD's in that thing. 

    There is different Config needs with INNODB vs MyISAM they dont use the same cache settings.

    I use a 6 core 12 thread server with 32GB of ram. and i can pull 400k daily users. 4-7 LA something is clearly screwed in your setup.

  5. For anyone wondering. Changing the engine of the database to InnoDB still seems that everything works nothing is broken. It has reduced the overall CPU usage from 80% overall to 10% spreading it over 3 servers using galera and using proxySQL to loadbalance between these 3 servers. So far this has speed up the website 5x 

     

    Before I did 900 queries a second now It pulls over 3000 using a stress test. And thats not close to its limits. If anyone is interested in how I did this let me know.

    • Like 3
  6. 59 minutes ago, Tech Support said:

    Unfortunately not, we never can have the timeframe due to high amount of support we do. The database scaling as we see it is still a long way, it will require full frontend code rewritten to the nextgen API. For now we only have a fracture of API and rewritten few blocks, 9 out of 59. When we finish the admin panel, we will return back to API and blocks refactoring. I hope this will get faster, as the API is partially ready. Initially we were planning to have this done till the end of last year, but then management decided we should push to the new admin panel GUI, and this took much longer than it was initially expected.

     

    For now we don't have any plans to move to InnoDB. The MyISAM in 2008 was considered as higher performance than InnoDB (because InnoDB has overhead for transaction handling and isolation levels), and also InnoDB in 2008 didn't support full text indexing. Even now many customers still have MySQL 5.5 and InnoDB started supporting Full text search starting with 5.6. So the dilemma is, if we want to move to InnoDB we will have to require MySQL update for many of the customers, and to be honest for now we don't see any benefit from this.

    Moreover, if you want to move to InnoDB you can do that yourself, there is nothing in KVS that prevent you from doing this. The only issue is that any new tables we add with new versions will still be added as MyISAM and you will have to do database update manually and to make sure all new tables are changed to InnoDB. I think some customers are doing like this, some customers switched to InnoDB already.

     

    Do you mean database load balancing or front end load balancing? KVS doesn't support database load balancing officially due to technical reasons, not due to licensing.

    For the frontend load balancing KVS supports load balancing by using satellites. However this increases database load and if your database is big, there is a problem with database overload.

    Oright I will do some tests with Innodb and clustering it so see if I can get it to work. 

    I did mean front-end loadbalancing but if its possible with satellites then I will give that a shot. 

    Thanks for the answer

  7. Do you guys have any timeframe on when to add sort of scaling options? For instance:

    I cant use Galera type cluster because myisam is in use. Do you guys have any plans to move it to innodb? Kinda confused why Myisam was chosen as a design choice. 

    I cant use any form of loadbalancing because that would be against the license agreement.

    I am kinda struggling to scale the website I have because the SQL server is struggling to keep up. There is no scaling to be done here.

  8. 19 hours ago, Kvslover said:

    Please can you kindly recommend any good css developer for me? This has to be done by trusted and identifiable person.

    try help me 

    I can vouch for there guys, Did and still do terrific work for me.

     

×
×
  • Create New...