i thought this performance issue was resolved with the latest File OE version ?  I always delete checkpoints from oldest to newest to older, not sure if it makes any different but that's how i do it. I don't think it matters one checkpoint or many checkpoints, file system is doing COFW so if there was any issue related to that it would happen even with just one checkpoint.

don't remember, looked through some of the release notes

Which File OE version would that be exactly?

Deleting checkpoints now and it seem to be going well.  Once all are gone, will I see my savvol space per file system change right away or is there some clean task that must be done?  That is another reason I am removing these is to get needed white space back from bloated savvol space.  I am only using 3% of 5.6TB of savvol space at this time.  I hope to get that back and maybe start up checkpoints again in the future.

savvol will be released as soon as all checkpoints are deleted (including any checkpoints used for replication)

Ok, so, even if I delete the 42 checkpoints I created via a schedule, my 5.6TB of savvol space will be there until i remove the replication checkpoints?  yikes!  I am replicating this filesystem to a secondary site.  How do i clear out the replication checkpoints and then let them start again?  Do I have to pause or stop replication?  Will I have to begin replication anew?

Nope, replicator needs internal checkpoints ..changes between two replicator checkpoints determine what has changed/new and needs to be replicated .

delete replication and start fresh

Then will having to use checkpoints for replication to work also cause a hit in performance?

I cant pause replication, delete the existing checkpoints and un-pause replication?

potentially, you probably have seen this discussion by now

https://community.emc.com/thread/116347?start=0&tstart=0

What is the impact of deleting the checkpoints and starting replicator fresh? is it a full copy resynch?? Or via the checkpoints an incremental only?

if you delete replication, that in turn deletes two "hidden" checkpoints that are used specifically for replication ..and that means full resync.

Unless you have a synchronized user checkpoint there

In that context - no