Word 2016 typing is very slow

I am using a standard release of Office and running Word 2016 build 16.0.6701.1029. I have LG Ultra book product ID 00326-10000-00000-AA069. i5-4200U with 8GB.

I have found something that seems to make some difference (I say seems as it is early days). If I save the document in my OneDrive folder and work on it from there. This seems to have resolved the worst of my lag issues. If I do not work in OneDrive word is unusable.

Fair enough. I concede that the whole problem is probably not specially  an a Win 10 "Insider" version issue.

But I still believe it is specifically a Win 10 / Office 2016 issue!  I have seen several reports of similar performance issues from, people running that software on i5 and i7 CPUs with 8GB or more of RAM.  On that sort of "high end" hardware Office performance should be effectively instantaneous.  Given that there are many more people happily running Win 10 / Office 2106 on significantly lower powered machines  I am even willing to concede that many (not all) of these performance issues will ultimately be identified as driver issues.

As a software developer myself, I wholeheartedly agree and understand that before your can "solve" a problem you have to be able to recreate it. I frequently include that statement in my replies to other questions.  But it is not just files you need to recreate these problems. I believe that you will also need to recreate explicit hardware / software / driver configurations to catch many of them.

I understand that it is simple reality that compared to the controlled Apple hardware/software environment the Windows situation is wide open.  To do this sort of investigation MS is going to have to give us, the "average" user a tool that can hoover up the full hardware/software environment so we can give it to the developers along with examples of the problem files.  I'm sure that the existing Win 10 "telemetry" spyware can capture that info.  We the users just need a way to trigger it and capture the results so that we can forward the whole bundle (environment and example files) to the developers. 

Certainly it is reasonable give the developers time to do their investigations and come to their conclusions (I've been there, done that).  But I emphatically cannot accept "we can't reproduce it, sorry" and let it be so! This is bleeding MS with "more money than god". They can afford to take the time and money to find and fix these problems, in conjunction with the driver makers if necessary.  MS so proudly trumpets that Win 10 is running on 300 million machines. If this sort of problem affects only 1% of installations (I'll even grant it is probably not that high), that is 3 million users who can't use expensive hardware and software for the purposes they explicitly bought it for. 

Let's face it, on the other side how many users even know of this forum to post their questions on. I'm sure it is way below 1%, more like 1% of 1%, so using simple math, each complaint represents a lot of unhappy campers.

It certainly is true that I'm running a pre-release version of Windows, @Rohn007.  However you've nothing to base your assertion that the problem is an insider release issue since (a) "I cannot confirm whether I had the issue prior" inherently includes that one doesn't know and therefore the issue may have been there before I joined the insider program, (b) discounts the same reports coming from @ZahirDhalla, @KayOtto, and DanielRibeiro_16, and (c) discounts your own statement in this thread, "[t]he problem is first being able to recreate the problem ... You can only chase down a problem, where the "code is spinning it's wheels", if you can consistently recreate the problem."

In order to recreate a problem and get to the root of it one needs data to analyze and in this case that data starts with the Word files themselves.  Investigation could most certainly find that [in my instance] the insider build is at fault and everyone else's reports are just their imaginations running wild, or the investigation could find that my file sample is able to reproduce the issue on another install somewhere and point the devs to a fruitful direction.  Let's say we give the devs a chance to look it over and come to their own conclusion.  And if that is, "we can't reproduce it, sorry." than so be it.

Since this appears to be a Windoze insider release issue, you should post the question on the windows insider forum ...