Trevor Petersen
Problem: This project was aimed at introducing postdiction, a lossy reduction method designed for databases, to the distributed setting. Postdiction can have significant computational overhead and slow execution times, expecially when compared to other lossless compression algorithms. This inspired the search
Approach: The main way this problem was approached was by introducing fitting methods to the postdiction process. Previously, postdiction would use all of the data given to it to train its models. This was changed into a two-phase approach: first a training phase then a fitting phase. The training phase would use a sample of the data to create the models, and the fitting phase would fit all new points into their model. One important consideration during both of these was ensuring that our program error threshold (defined by the user) was never violated. This threshold ensured that all values recovered via postdiction are within error range of their original value.
I tested three different fitting methods for this project:
Results: The outcome was that Method 3 seemed like the fastest option for processing data and was able to outperform the speed of training. Additionally, fitting can occur on many different cores, devices, or machines, which can offer even greater speed ups.