Is it a good idea to split a Drupal site into multi-site one for editors/admins and another for front end users? To illustrate:
I have a multisites with a shared db edit.example.com and site.example.com. They share many tables but do not share all (a work in progress to determine what exactly need to be share). For example, the system table is not shared in order to be able to control what modules need to be enabled across all, on edit.example.com only and on site.example.com only. Does this can help performance? 
Is this a good idea or is it just adding an extra level of unnecessary complexity?For example I see caching becoming a problem because cache_page is not shared, or even if it is shared.   

If there are any references out there please refer me to it.
Is this a good idea or is it just adding an extra level of unnecessary complexity?


There is no functional advantage of creating a multi-site for the purposes of separating content administration, as that will add an unnecessary level of complexity.

Some of the issues include determining what tables to share (which you've identified). Another common scenario is that content will be rendered differently depending on the site, leading to troubleshooting nightmares. An unscrupulous developer can have multiple versions of the same module in the site code, which creates head-scratching differences.

A single site is significantly easier to manage and ensure that administrative roles and permissions are logically set given your needs.

It can be helpful to have a distinct administration theme to visually enforce the difference between a normal and administrative roles. It's possible to specify a role per theme - https://drupal.org/project/role_theme_switcher for example.