Database change (Redis) and recent updates



In this post I am going to tell you guys about the recent changes at BeeIMG that were made during the past few days.



We did a major change in storing the image views. We changed from MySQL to Redis, which will hopefully decrease the image serving time. If we had MySQL further soon it will get overloaded due to the high image views we are receiving. only image views are stored on Redis and every 30 minutes the MySQL server will also get updated. so you can only view live stats via the image view page.
we also cached the stats page memcache so the it does't create much turbulent in the server(Redis). It will be only cached for 2 minutes.



we also removed cloudflare caching and it will be only activated when the sever is on high load. our plan with NetDNA for CDN will expire on August and I am not very much happy with their service. The reason is that they are very expensive and their Asia nodes have to be bought separately as a add-on and the add-on too is very expensive. so I have planned to move to cloudflare after August as cloudflare has Asia nodes,they are fast and mainly cause they are free.



During the past few days the Reputation system was giving out errors and did not work properly. The first coded reputation system was a bit confusing for me too. So I decided to re-code it from the scratch. This time I tied to stay simple and it worked. Now it's really easy to understand and use 80% less MySQL queries than before. but there was catch. I had to remove the Reputation page which I believed gave no use to users and used up space in the database. As the reputation system uses less queries now it update every 30 minutes also you can manually update it too. Now the Rep points will be awarded as follow,



For a uploaded image - (+1) point
For voting on a image - (+1) point
For a positive vote on you image - (+1) point
For a negative vote on you image - (-1) point
For making a album - (+1) point



And as you can see we also changed the our blog template. There was also some smaller changes and updates that doesn't worth mentioning here.
If there is any problem,a bug or a feature you would like to be implemented on BeeIMG don't hesitate to contact me from here.



There will be more updates as well as upgrades to run BeeIMG smoothly and as you like it. Also I am planning to post some the codes that BeeIMG is made of, on here on the blog. so stay tuned... Thanks for reading :)

Comments

Post a Comment

Popular posts from this blog

Stability Improvements 2019

Hello all, Over the past few weeks BeeIMG has been a little unstable and just wanted to clarify on what happened. In the first unstable issue which in November were caused by our server provider doing maintenance on our servers. Our AMS node got hanged up during the maintenance and had to be manually restarted. However the impact on the service was minimal and the maintenance on our CDG node affected our service as its where our databases is hosted. After the maintenance the db server had been moved to under performing hypervisor and started to slow down the site. We had to move the server again to a better server. Forward to December, one on of our free customers started hitting with lot of image view per second and this overloaded memory on AMS server and to redis node to fail. Making maters worse AMS server ran out of disk space. when a fail over to CDG happened the traffic overload that servers redis node and caused the service to fail. The site served 503 errors durin...
Read more

Amsterdam Server and Forum

Hello all, Some of you may know that we had a 2 hour of downtime at the end of the last month. It had caused us to rethink the single server situation. As you some of you are expecting reliable uptime from BeeIMG.
Read more

Recent Hiccups May 2016

We faced some blackouts recently, and it was because we got very popular in china. The images that was generating lot of traffic were violating our TOS, but as they were generating lot of traffic and I thought it was a good time to stress test our image delivery systems. At first we were handling the load fine. after some time our redis server start acting wired. the issue was with dumping the db to disk, but as the images were generating lot of data the redis server crashed. we started to migrate the all gif images to be served by our CDN while still collecting views data. but at some point our real time stats handling script started to fail due to redis connection issues. after that the data started to collect and the redis server crashed every time it was started. While all that was happening we noticed that our php front end started throwing errors. this was due the connectivity issues to our redis server. The image serving end do not use redis server and was not afflicted. its usi...
Read more