I have been doing some cleaning up in the database of one of my WordPress installs, and I noticed that the wp_options table was about 2.1mb, and had 1200 rows.  I've gotten it down to around 800 rows, and 1.2mb.  However, there are a bunch of transients.

Should I remove these?  I know they don't autoload, so it probably isn't causing strain on the database.  

Most of the transients have formatting like the following:

_site_transient_browser_03df11ec4fda7630a5...
_site_transient_browser_065e09a1287aadfb4d...
_site_transient_timeout_browser_03df11ec4f...
_site_transient_timeout_browser_065e09a128...
_transient_feed_1a5f760f2e2b48827d4974a608...
_transient_feed_f8e8c12cc5c787789728d7481a...
_transient_feed_mod_e6460a14e5784b3ee64f91...
_transient_timeout_feed_1a5f760f2e2b48827d...


So, is it worth taking the time to remove these? 

Thanks for reading!  Any thoughts are appreciated.


Question: Kosher salt vs. Table salt for rib eye steak
Answer: The reason people choose Kosher/Sea/Rock salt over table salt is mainly down to the crystal size and the lack of additives like iodine.

Kosher salt is less soluble and less dense than table salt.

The large crystals in these salts mean that unless there is a fair bit of water present they don't completely dissolve. This means it is less likely you'll over salt steak even if it's caked in crystals.

Table salt will dissolve with far less water present and will, therefore, get absorbed more easily into the meat. 

Also the lower density means you can liberality sprinkle Kosher/Sea/Rock salt on things and even if it does all dissolve you've actualy added less salt than you would think. It looks like a lot but 1g of Kosher/Sea/Rock salt takes up a lot more space than 1g of table salt.

1tsp table salt would be way too much. I'd go for about half the volume of Kosher salt if you were dissolving it in liquid and maybe as little as quarter the volume if I was using it as a rub (as in salting a steak).