could sayu get dazed from lag
This is gonna get long and stupid probably, but I want to talk about this and my thought process! If you just want to skip to where I talk about how the lag would feel, then just head straight to the bottom and start reading the text that’s in list form :3
Okay, so first off, let’s define lag: Lag is a slang term for a noticeable decrease in application speed, due to extreme network congestion or insufficient processing power. When traffic is heavier than network capacity, the network requires that a program wait before sending or receiving data.
This would mean, going off of the sentient Sayu headcanon (since if we go with just program Sayu then this question doesn’t matter because ze doesn’t have a consciousness and can’t get dazed to begin with) along with adding 1010 into the mix, they would need to experience lag first. Considering that Sayu and 1010 are all very high ranking NSR members, along with Neon J being proficient in coding and tech, I would say that both Sayu and 1010 have their own personal server (either individuals or shared doesn’t matter because of just how little the numbers are).
Not only that, they are all most likely built from the top of the line equipment and cooling systems, allowing them all to process their surroundings at extremely fast rates. From audio, video, sensational, possibly even taste and smell receptors, all of these would normally take up a lot of space and power but since we are working the MKIII units (and Sayu would benefit from all the knowledge since I am sure ze would use their same or similar schematics) that would mean that these sensations have been streamlined into their design, allowing more space for processing.
Even with these powerful processing systems and servers, I bet Neon J would make backup systems for everyone. He would definitely make it so that both Sayu and 1010 can be off the servers/internet (which means they would literally not be able to lag) but still be able to function. Offline, their harddrives would be limited, but they would still have ample amount of storage space and, if offline by choice, they would sync up with a network every hour or something like that for a few moments to refresh their minds and make sure to have an up-to-date save of their systems. If they are FULLY offline, most likely from an unwanted disconnect, and can’t sync up, then their minds/harddrives would start to fill up depending on how long they are offline. They wouldn’t experience lag, since they are offline, but they would start to see an uptick in their processing power and cooling systems to try and keep up with their limited storage. Thankfully, since it is not ideal to stay offline for long periods of time, 1010 and Sayu try to stay fully connected or have periodic sync-ups to keep them from slowing down.
Now, when online, for Sayu and 1010 to even experience lag, considering their state-of-the-art designs and personal network(s), that would mean their servers are becoming overloaded. Either from too many things to process at once or their servers are experiencing some issues.
In the case of too much to process, it depends on if the server is an individual or group server. Individual servers (one for each 1010 and Sayu) would be the least likely to experience lag. On the other hand, group servers would see lag more often (not saying it would be common, but it would happen more than an individual server) since the server is dealing with the processing of multiple robots. 1010 and Sayu would also need to be FULLY ONLINE to experience lag since they would be dependent on the servers, otherwise being halfway offline or fully offline puts more power/responsibility onto the hardware of the robot.
Individual servers are weaker than group servers because they only need to accommodate one robot. Because of this, new experiences that were not planned can slow down the processing power of a robot and cause a VERY SMALL amount of lag, but it is usually not noticed because of lag compensation.
Group servers will need most or all members to be at a high processing power in order to start lagging. So if only Sayu is experiencing a new scenario with a lot of sensations (such as a concert in a new area with new features) then the group server will be fine while an individual server would start to stutter. But if most or all 6 members started to get overwhelmed (such as 1010 being attacked by B2J, since Sayu would have already been offline) then they might start to lag. For 1010, they have a way to negate group lag by syncing up and making it so only one or two robots needs to control the movement of the whole group, which severely reduces the potential lag, but if not synced up and are continuously exposed to high demanding situation, they will experience lag (and if Sayu was on while all of 1010 were lagging out the server, ze would start lagging to).
In short, this means that it takes a LOT to make 1010 or Sayu lag. And if they are starting to lag, then that means the situation is already very stressful and upsetting for them and the lag they are experiencing is either not noticeable at the moment or they are starting shutting down unnecessary systems while boosting the systems that will help stop the lag. They might even just shut down entirely so that they do not overheat and cause permanent damage, or because they literally cannot handle the situation and shutting down will be better for them mentally and physically so they can be repaired.
Okay, so I know all of this was just me talking, but going back to your question on if Sayu (or 1010) would become dazed if they lagged? I would say... It depends. There are many different ways that a robot might experience lag. I’ll list a few that I think are likely to be happening.
-They just fully shut down whenever there is lag because of the high amount of stress the robot would need to be in to get any noticeable lag. This is not an ideal response at all, but it definitely is possible. Basically this is the equivalent of passing out as a stress response which can be dangerous physically depending on where the robot shut down along with mentally because a forced shut down can lead to file corruption.
-Shutting down unnecessary systems and boosting helpful systems until the servers are cleared or reset. When doing this, the robots would lose most of their sentience and basically get rid of their personality temporarily, leaving them to run on basic coding as a survival tool until they can properly run all their systems. This is better than the above option because it keeps the robots working with little chance of file corruption, but they cannot perform or meet with fans because they have no personality. This is the equivalent of blacking out, where your body is still working and doing things, but you will not remember or will vaguely remember what went on while you were out.
-Lowering the quality of sensors to put less pressure on the servers. This would be turning their highly sensitive hearing down or making their video receptors only display in 144p instead of something like 4K resolution. Doing this allows the robots to stay functioning and keep their personalities, but it causes their reaction time to become severely dulled. This is the preferred option if the robots do not need to have direct interactions with fans, so preferably on stage following their set code/routine, in the privacy of their own home, or someplace where they can be safe in solitude. The equivalent FEELING of this, would be not having slept in a few days, where your senses are very dulled and sometimes you need things repeated a second time or need to do a double-take to make sure you saw something correctly. This doesn’t mean that the robots are tired, it is just an equivalence, this behaviour can take place at any point in their charge cycle.
-Finally, not doing anything to compensate for lag. Obviously, this is not the best option, at all. Staying on without lowering or shutting down any systems will cause the robot to experience the equivalent of extreme overstimulation (overstimulation can be felt without lag, so lagging and being overstimulated is a horrible experience). The lag will start to mess with their senses, causing random noises and notices to pop up and stay up with no way to send them away, make vision highly pixelated, blurred, and over/underexposed, sometimes even freezing their video feed, and even cause their body to react on heavy delays which can lead to the robot walking over a ledge or into traffic or knocking things over and breaking the stuff around them. At this point, a full server reset would be needed along with a shutdown of any robot who did not do any lag compensation. Once brought back online, the robot will need to manually readjust a lot of their settings and need a long break to make sure the server is fully operational and their connection is strong along with making sure they have mentally recovered from their ordeal.