I installed the module and it worked fine ... but from the very moment of install my localhost started suffering frequent errors ... Warning: MySQL server has gone away query: INSERT INTO watchdog... errors. Sure I can change the my.ini file ... but I use the localhost as a gauge of resource intensity for the overall website and this module really pushed it over the limit.

Wonderful concept, and I was really looking forward to using it. Any chance this can be made less resource intensive?

Comments

berliner’s picture

Status: Active » Postponed (maintainer needs more info)

That surprises me. I am running a local install myself to do development and testing and I never faced this kind of problem. What messages are written to watchdog that are related to this module? I could only imagine some kind of installation error. Could be also that a special combination of settings is causing this. Please give me more details and I will certainly try to fix this.

rkodrupal’s picture

Thanks for getting back. Following your hint I did a fresh reinstall after setting my.ini to higher values. Then I reset my.ini back to its original (lower) values. Seems to be working okay for now. I'll play with it for a week or so and let you know how it goes.

rkodrupal’s picture

Version: 6.x-1.0 » 6.x-1.1

note: I have a very resource intensive home page and i'm running localhost on a very resource constrained laptop (Evo N410c).

I cleared out all the caches (and cleared out all temp files on the laptop) for both tests.

Running localhost with Sticky Notes (1.1 installed)
time to load of the homepage: 34 seconds

Running localhost with Sticky Notes disabled
time to load of the homepage: 22-25 seconds (ran twice)

I noticed with Sticky Notes installed that the home page initially shows up at around 27 seconds (approx. same as disabled), but that the sticky note itself doesn't show up until 34 seconds.

I read elsewhere you were working on a rewrite of the script. I hope this helps in reducing the timing.

berliner’s picture

The delay between page load and display of the notes is due to a separate HTTP request in order to load the notes after the page has been loaded. If you have some thing like firebug than you can easily see this request, probably as one of the last ones. It get's triggered as soon as the dom is ready. The mentioned rewrite doesn't really touch this logic and focusses instead of proper code, maintenance and more possibilities to integrate other features in a proper way.

The reason I decided to trigger a separate HTTP request was that I wanted the notes to appear without any necessary editing of template files or the need to add a block somewhere. It was the easiest method I came up with actually. Also I didn't think that the additional page load would have negative effects, because it happens only after the dom is fully loaded and the site has been completely rendered.

For the reasons you stated I would consider to make the described an optional (but default) behaviour and to allow the admin to print the notes themselves in the page template.

rkodrupal’s picture

I guess I forgot you were essentially loading two nodes ... hence the delay. The 25 seconds on my localhost equates to 2.5 seconds on the host provider machine ... hence there will probably only be a .5-1.0 second delay for the notes (and I'm assuming much less once they're cached).

... let's hold off on any changes on this until i get this uploaded to the production site (which will happen after further testing on localhost) and can really see the response times.

Thx for your prompt replies.

rkodrupal’s picture

slept on it last night, and it occurred to me that most of the posts on my site will be static. I'm using sticky notes as a 'call out' feature, as in 'you SHOULD read this page because...'. Hardcoding the notes was an option I considered, but Sticky Notes offered additional desirable features:

1) ability to see all the sticky notes in the overview (i.e., see all the 'you SHOULD' notes)
2) ability to hide all the sticky notes on a page with a single click

your suggestion in #4 might actually be a better answer for someone with my needs?

again, great module. thanks for coming up with the idea.