The LTB Network Forum

Your servers seem a bit slow!

Back to LTB Platform Development & Support

Comments

• Rob

  

  Offline
  Posts: 604
  Location: California

  @cryptonaut

  While I don't know much web development or servers, I noticed some podcasts use the identical visual image several times, however it's different JPGs that are bing served:

  New Bitcoins & Gravy image 172k X 3 uses Standard Beyond Bitcoin image 211k X 3 uses Standard P2P Connects Us image 117k X 3 uses

  I know it would be a manual short-term patch (if it's even doable), but if you could have one JPG for each instance (instead of three), that would save a total of about 1MB of traffic per home page view. And if you could somehow give content creators an option to just reuse previously uploaded JPGs, rather than making creators upload a new JPG with each submission, maybe that could be a longterm way to slim down the amount of image data your servers need to deliver for the home page?

  Posted on October 15, 2014 at 3:44 PM
  Permalink
  1 like
• deweller

  

  Offline
  Posts: 347
  Location: Nashville, TN

  @cryptonaut

  You can also use Cloudflare. This will take the strain off of the servers of having to serve the same images, CSS and JS over and over again.

  I have a feeling the real performance bottleneck lies elsewhere. But Cloudflare could help in the meantime.

  Posted on October 15, 2014 at 3:49 PM
  Permalink
  0 likes
• mdw

  

  Offline
  Posts: 126
  Location: orphaned block

  I think @deweller is right, no real chance multiple image issue is a significant factor, except for those for whom bandwidth is the biggest issue. A CDN would certainly speed things up for most users. But I really hope we don't go with cloudflare. They're pretty hostile to Tor browser now, requiring captchas to be completed on every pageload.

  A dropdown list of previous images for authors to choose from would help the page load time slightly for the homepage when more than one episode is displayed on homepage using (what looks like) the same image.

  What might help more is to serve images from another subdomain, i.e. img.letstalkbitcoin.com Browsers, especially older ones, like to limit the number of open connections per domain. Images would be served from a different host, therefore downloaded in parallel with all the other files.

  Note that this makes scaling the site easier too, as the subdomain can initially reside on the same physical server, but be moved as traffic grows. There are plenty of other neat tricks, and I'm sure @cryptonaut has some things planned, but the real issue may be manpower and prioritization.

  The backend (esp database queries) is the place to look for bottlenecks if the server response times are slow. To be fair, there's a whole lot of features being added, and until it becomes a real pain point, it'll probably not become a super high priority.

  Isn't that just how life goes? Always tradeoffs :(

  Posted on October 16, 2014 at 12:07 AM
  Last Edited: October 16, 2014 at 12:16 AM
  Permalink
  0 likes
• Rob

  

  Offline
  Posts: 604
  Location: California

  Good to learn from people who know a lot more than I do!

  Posted on October 16, 2014 at 6:52 AM
  Permalink
  1 like
• Cryptonaut

  

  Offline
  Posts: 1944
  Location: Canada

  CDN for the images, javascript etc. could be a good idea, I would probably go with amazon AWS over cloudflare though.

  The main bottleneck is the database actually. Looks like some of the queries regarding getting blog data (which happens on every page due to the media player up top) are showing up as taking up to a couple seconds each, which is not good. Need to optimize those queries and reduce the amount made in general.

  I think part it of it some of the extra data (e.g for media player) that the LTB system theme grabs. For instance, comparing these 2 basic content pages:

  http://letstalkbitcoin.com/about-us
  http://ltbcoin.com/

  They are both running off the same server, same database, same installation (CMS can handle multiple domains). ltbcoin.com link loads a lot faster than the other one.

  Posted on October 16, 2014 at 8:40 AM
  Permalink
  0 likes
• Cryptonaut

  

  Offline
  Posts: 1944
  Location: Canada

  I found one of the queries that was causing a major bottleneck, looks like the site is loading in a decent amount of time now.

  Posted on October 16, 2014 at 12:43 PM
  Permalink
  1 like
• page

  

  Offline
  Posts: 423

  @cryptonaut I found one of the queries that was causing a major bottleneck, looks like the site is loading in a decent amount of time now.

  Yes, much better. I don't think it was to do with the media player though, was it something else?

  Posted on October 17, 2014 at 10:45 AM
  Permalink
  0 likes
• bitgears

  

  Offline
  Posts: 144

  Today the website loading times are faster, nice work!

  Posted on October 17, 2014 at 10:52 AM
  Permalink
  0 likes

Post Reply