Kiwitrees on Twitter

    footer, timeout, googlemaps, Search and replace, release, Support/Bug Reporting, BURI, locked out, descendants, Histo, calendar.php issue, login upgrade, clippings cart, contacts, server, help, age, shared note, getClientIp, php 5.6, name, special character, 3.0.0, seo, error, sanity, simpl_research, login failure, .mo, 3.1.1, random_media, bug, colors theme, GDBR, dead, zend, custom modules, nickname, translate, tree, ID facts, translation, edit, missing data, feedback, json, F.A.B., kiwitrees-nova, 3.2.1, login, marriage, performance, MAC, DIV, My Page, custom, 3.0.0. setup, Favourites, road map, resources


    1669 posts

    No problem. I thought by deleting the logs, like cache, would reduce my size for loading site.

    Yes, that is correct, and you should do it, But that is not doing it “at your web host end”. In many or maybe even most (I don’t know for sure) cases that is sufficient. But in some cases it will not. Only your web host can help in that case. But try it – delete all your logs and see if it results in a reduction in the size of your database.

    But if you mean by “loading site” the speed at which pages load, then no, the size of the log files will not matter, except when you load the logs page.

    My personal kiwitrees site is