WF Table Documentation/usage?

  • Resolved SchaOn

    (@schaon)


    6 years, 9 months ago

    I would like to switch some tables over to MEMORY type as that’s supposed to be the fastest for read/write… though, if the server restarts, or needs to wipe that memory… then those records are gone – which for some of the tables that’s probably fine tbh.

    So, curious, what tables would be safe to do this with on the WF Tables? Sadly, I can’t find any documentation on what each table is used for. (is there a link somewhere?)

    I’m thinking:
    -wfliveTrafficHuman
    -wfReverseCache
    -wfSNIPCache
    -wfStatus (unless you want to keep the status after a server restart, but it would just rebuild with the new status anyways)
    -wfVulnScanners

    Curious, what are the other tables for? like BadLeechers, Crawlers, Hits, etc, etc, etc

    Obviously, you would want the BlockedIPLog, Blocks, Blocks7, and BlocksAdv as a permanent table…

Viewing 1 replies (of 1 total)
  • wfdave

    (@wfdave)

    6 years, 9 months ago

    Hi @schaon,

    Note that these tables are from an old version of Wordfence, so they are no longer used.

    wfBlocks
wfBlocksAdv
wfLockedOut
wfThrottleLog
wfNet404s
wfBlockedCommentLog
wfVulnScanners
wfBadLeechers
wfLeechers
wfScanners

    I’ve written a small summary of all the tables. If you decide to use memory-type for a table, this is what would not work.

    wfConfig – All Options
    wfCrawlers – Block fake crawlers
    wfHits – Live Traffic
    wfHoover – URL scanning in posts

    wfLiveTrafficHuman – Determines bot / human
    wfLocs – IP -> Country, country flags in live traffic
    wfLogins – Firewall -> Login Attempts
    wfNotifications – Notification badge

    wfReverseCache – IP -> Hostname lookup
    wfSNIPCache – Wordfence Security Network
    wfStatus – Scan -> View Full Log
    wfTrafficRates – Enforces Rate Limiting

    wfFileMods – File scanning
    wfFileChanges – ^
    wfKnownFileList – ^

    wfPendingIssues – Issues from Scan Results
    wfIssues – ^

    Some of these tables are used for caching results from very long operations.

    For example, the wfReverseCache is used when an IP is reversed into a hostname. Looking up a hostname can take a few seconds, but once Wordfence has stored the hostname+IP into wfReverseCache, the next lookup will be near instant.

    So I would recommend not changing your Wordfence tables into memory-type as this would clear all the cache whenever your server restarts.

    However, if you don’t use some of the features such as Live Traffic, or the Security Network, you can change those tables into memory-type.

    Dave

Viewing 1 replies (of 1 total)

The topic ‘WF Table Documentation/usage?’ is closed to new replies.