tree 95e3f785ed2054ce6231cdc81b8c62118aad705f
parent c69ac53848a8f4c3e927bd048be0d35cf0dfb253
author Nikhil Kak <nkak@pivotal.io> 1582067074 -0800
committer kaknikhil <kaknikhil@users.noreply.github.com> 1583518689 -0800

DL: Remove final function for fit multiple

JIRA: MADLIB-1416

Based on our experiments, we noticed that at the end of each hop, fit
multiple would start using a lot of memory (from 80 GB to ~ 140 GB on
the master host of our gcp cluster) and we attributed that memory spike
to the final function.

Removing the final function brought down the memory to around 30-40 GB
and also made the places10 query 3 times faster

places10 with 20 msts on a gpdb6 cluster with 20 segments
```
With fit multiple final function
~ 2 hours per iteration with memory hovering around 70-80gb and peaking
at around 130-140GB at the end of each hop.

Without fit multiple final function
~ 35-40 mins per iteration with memory hovering around 30-40 gb and
peaking at around 40-45 GB.
```

Co-authored-by: Ekta Khanna <ekhanna@pivotal.io>