velospace is about bikes and the people who ride them marketplace photos random forums














    • CommentAuthorgreg
    • CommentTimeMay 7th 2011 edited
     
    Over the past 31 days velospace has had 0 seconds of downtime - this is an accomplishment given the past six months of instability that we've had. I want to thank all of you who suffered through the crappy response times and outages for sticking around as loyal velospace users. You guys are awesome

    • CommentAuthorquidose
    • CommentTimeMay 7th 2011
     
    Yay!
    • CommentAuthorjesmerl
    • CommentTimeMay 7th 2011
     
    can i get an amen!
  1.  
    woot woot. Very impressive. Thanks for all the thankless hours you put in Greg.
  2.  
    i believe it. i lurk on here forever sometimes.
    • CommentAuthorrollins
    • CommentTimeMay 7th 2011
     
    jynx
  3.  
    Hey, as long as we don't have another photos crash, ok?
  4.  
    Wow! Alright! Thanks, Greg!
    • CommentAuthorSplined
    • CommentTimeMay 7th 2011
     
    Good work and thank you Greg.

    Much appreciated

    Splined
    • CommentAuthoreaglerock
    • CommentTimeMay 8th 2011 edited
     
    greg, any idea from the log files what the change was that put in the fix?

    I swear, that sentence made sense in my head.
    • CommentAuthorAaron C
    • CommentTimeMay 8th 2011
     
    I had noticed a massive improvement in the way the site runs,

    thanks greg.
  5.  
    Dear greg,
    You rock.

    Best,
    Your fans

  6.  
    Cool.

    But....

    The bike image galleries need a ton of work. On one of my bikes when you click on a thumbnail, a pic of someone else's bike shows up as the big picture.
    Not to mention it takes forever to load them from the thumbnails. Do you store them in the mysql database or something?
    • CommentAuthorveggie
    • CommentTimeMay 8th 2011
     
    Posted By: squiresuzukiThe bike image galleries need a ton of work. On one of my bikes when you click on a thumbnail, a pic of someone else's bike shows up as the big picture.


    User error most likely.
    • CommentAuthoreaglerock
    • CommentTimeMay 8th 2011
     
    Posted By: veggie
    Posted By: squiresuzukiThe bike image galleries need a ton of work. On one of my bikes when you click on a thumbnail, a pic of someone else's bike shows up as the big picture.

    User error most likely.

    Yep. Uploading photos with names like "IMG_5280.jpg" and "IMG_5282.jpg" has a high probability of producing unsatisfactory results.

    https://velospace.org/forums/discussion/471/why-if-i-post-my-pics-does-a-different-bike-show-up/

    https://velospace.org/forums/discussion/867/website-problem-my-pics-not-my-pic/

    https://velospace.org/forums/discussion/1069/lets-see-some-beaters/

    https://velospace.org/forums/discussion/1618/posting-bike-pics/

    https://velospace.org/forums/discussion/1936/uploading-photos/

    https://velospace.org/forums/discussion/2666/cant-upload-pictures/
  7.  
    Also, I think that if you read the page where you load your images there is a disclaimer warning you to not make that mistake.
    • CommentAuthorgreg
    • CommentTimeMay 8th 2011 edited
     
    Posted By: eaglerockgreg, any idea from the log files what the change was that put in the fix?

    I swear, that sentence made sense in my head.


    Yes, I am able to attribute the improvement in uptime and responsiveness (average page loading time dropped from 1500+ milliseconds to ~ 700 milliseconds) to tuning_primer.sh. This script analyzes MySQL runtime statistic logs and comes up with recommendations for MySQL variable memory and table size settings based on cache hits, slow queries, cache utilization, complex joins, open tables, and so on. It turns out that several of velospace's MySQL variables (particularly the engine specific cache ones) were too low for the site's use. After tweaking variables based on the tuning_script.sh recommendations I was able to get the site humming along perfectly. The database went from residing in about 700 MB of memory to about 2.5 GB of memory - the uptime and responsiveness gains are due to the fact that the database is no longer harddrive bound during regular operations.

    Of course, the other tweaks that I've done over the years have helped reduce the strain on the server (APC, IpHistory table optimization, switching from MyISAM to InnoDB tables, and so on). But the tuning_primer.sh script is what really makes things work.
  8.  
    Posted By: eaglerock
    Posted By: veggie
    Posted By: squiresuzukiThe bike image galleries need a ton of work. On one of my bikes when you click on a thumbnail, a pic of someone else's bike shows up as the big picture.

    User error most likely.

    Yep. Uploading photos with names like "IMG_5280.jpg" and "IMG_5282.jpg" has a high probability of producing unsatisfactory results.


    Yeah, but that's seriously really easy to fix. Just have PHP generate a random 10-digit number, then set it as the filename and enter the new name into the database. Or if you're worried about the 1 in 10 billion chance (that's the real chance) that it will generate a random number that's already been taken, then just have it check the database using the mysql WHERE clause. If it's already taken, then generate a new name and repeat.
  9.  
    This is a bug that's been here since day 1. It's killed most of my bike photos, in fact. We're all aware of it and have tried to fix the issue.

    If you actually want to put the work in to fix it, I'm sure Greg would be happy to talk with you about that.
    • CommentAuthorNash
    • CommentTimeMay 8th 2011 edited
     
    That is a IT nerd GOLD MEDAL! good work sir!!
 
\



velospace | about, FAQ & policies | contact | blog | status | site map
© 2005-2011 velospace. All Rights Reserved.