Bill Platt's dashboard

You can reduce your server processing by making us choose to auto-load scheduled tweets when we are editing and adding new tweets.

Right now, as is, I add a new tweet, then when it saves, it auto-loads my schedule. I have to wait for my schedule to load before I post a new tweet.

When I am editing, the edit window also insists to load my schedule for me.

If you could stop the auto-loading of my schedule when I am adding and editing tweets, you could realistically trim your processing power by 25%-50%.

If you can cut your processing at this level, perhaps you can keep from crashing every day around noon time.

Hey. Every day around the lunch hour, your system bogs down. Then each time it tries to restart itself, it Tweets the posts first in line. I end up with 10x repeats, which goes against the impression I am trying to convey.

I am trying to get all of my FutureTweets out of the heavy traffic lunch hour.

But you could help that by having the system bypass all scheduled tweets that are past time, if those tweets are daily's or weekly's.

If those tweets are going to come back around, it is better to miss one than to repeat it a dozen times. Don't you agree?