My application was only sending 3-1 byte notifications and 4-4 byte notifications in a time instant. I believe after 3 notifications all remaining data was dropped. So I suspect the 60-80 byte limit includes some overheads or is actually a packet limit.
Also this limit is extremely low, is there any plan to provide some additional buffering in the cpu? Especially considering if I am using ProcessCharCfg then its not possible for me to know which devices received notifications and which did not. I believe ProcessCharCfg will fail any time 4 devices are configured to receive value change notifications or an time 2 devices with 2 value changes occur in one time slice.
Take for example TI's accelerometer profile. If 2 devices register for characteristic change notification and then the device is moved, there will frequently be dropped notification changes.