By ochiburi on

I installed the Christmas Snow module, but immediately upon enabling it my response time dropped to about (literally, I am not exaggerating) 4 minutes per mouse click. So I was able to eventally disable it OK by being patient and working verrrrry slooooowly, and immediately performance was back to normal.

This is very odd because when I looked at the "example" linked in the download page, it worked fine (even though it did push my CPU usage sky-high).

Any ideas guys?

Cheers,
Laurence.

⋅ Categories: Drupal 4.7.x

Comments

Jim@drupal.be’s picture

Jim@drupal.be commented

The demo works fine here although the demo site isn't drupal but the original script i guess.
So on my site none of the image appear. Just small squares occasionally. FF IE7 IE6 don't display any images. Followed the manual but to effect.

Some delay in the use of the site. None of the links are working, nothing is clikable. site freezes for a few seconds ten returns to normal but no flakes.

The lack off a issue queue is giving me some concern. The module was released 5 day's ago. I wonder if there are working drupal examples of this module.

There are no stupid questions. Only stupid anwsers.

dami’s picture

dami commented

Did some local testing on my crappy notebook, it pushes CPU usage to almost 100% in a few seconds. I did some adjustment to snowstorm config values in snowstorm.js and was able to push down CPU usage to 50%. I am going to try this on a test site on my host, but here is the changes I made: 

  var flakesMax = 64;             // was 128
  var flakesMaxActive = 32;    // was 64
  var flakeBottom = 120;        // set to 120px which is height of header of my site, was 0 -- full page

The small squares you see is because the js script uses relative path thus image path is incorrect. The module file actually tries to fix it by inserting the correct path, however you still need to comment out this line in snowstorm.js file to make it work:

  var imagePath = 'image/snow/'; // relative path to snow images
sepeck’s picture

sepeck commented

I believe the readme indicates it can cause high cpu utilization.

You can 'disable' any module by removing it from the modules directory.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide