Performance Affecting Settings

Verify Local Headers and Cross Post Data
These options are useful, but require some extra on-line and processing overhead. If you have a slow connection you can speed things up by disabling these. You will have to decide or experiment if the benefit is worth the cost. Note that you will have to change these settings for each server.
Verify Local Headers
Server - Properties - Operation "Verify local headers when ..."
If enabled, Gravity sends the "listgroup" command (after first fetching the articles normally) every time you fetch new articles. Gravity will fetch the list of all available articles on the server and compares them with those articles in the local database, removing the expired ones. It is useful, when enabled, because you may never see expired articles. If you need a performance boost - do not enable it, or run it manually.
Ø    You can perform this operation manually at any time, even if disabled in Server Properties. Right click the newsgroup in the group pane and select "Verify Local Headers"
You may not notice significant effects with normal sized text groups. But in large groups the effects are significant and Gravity may appear to stop working after fetching headers.
In very large groups (usually binaries) the server may have several hundred thousand articles. Even if you only have 20,000 articles local, Gravity fetches all the article numbers. You will have to wait while Gravity downloads and processes more than a quarter of a million article numbers after fetching new articles!
So the moral of the story is: do not enable this option if you work with very large groups.
·       Tip: You can set up the same server twice. Either use a different server nickname in Setup, or use the IP address. This way you can have text groups in one setup (with verify enabled) and binaries in another setup (with verify disabled).

Cross Post Data
Server - Properties - Operation  "Include Cross-post data when ..."
When enabled, this allows Gravity to track cross-posts. When an article is marked read or deleted in one group, it will be marked read or deleted in all cross-posted groups. In order to do this, Gravity sends the "xhdr newsgroups" command and has to download and process the response. The option is useful and normally does not cause problems. But you can disable it.

Gravity's method of cross-post management may be counter intuitive. For example - we have an article posted to GroupA and GroupB.
Case 1: If the article headers are already  downloaded in both groups, cross post works as expected.
Case 2: However, if headers have been downloaded for GroupA, but not GroupB, and you mark the article read in GroupA, when you download GroupB, Gravity will skip the article and you will not see it in GroupB at all, even with an "All Articles" filter.
The solution for Case 2 is to download headers for all groups before reading.
Some users disable cross-post management because of this. But remember that Gravity was designed as an off-line reader to minimize on-line time and bandwidth.