pergamonmystic:linkedhelp:patience
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pergamonmystic:linkedhelp:patience [2021/09/29 11:00] admin |
pergamonmystic:linkedhelp:patience [2021/09/29 11:14] (current) admin |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| ==== Desktop vs. Online ==== | ==== Desktop vs. Online ==== | ||
| - | In a **desktop application**, all activity taking place is within the memory of the computer on which you are working - and computer memory is //extremely// fast. The biggest impacts on speed which you will encounter in this environment is data access to a hard-disk, which is still largely a mechanical device and therefore is extremely slow by comparison; and, redrawing the screen when a long process is being undertaken. In this latter case the speed delay is not because the display is slow, but because operating systems typically regard screen updates to be the least important of all of the actions being undertaken (i.e. the //process// of adding 2+2 is regarded as more important than updating the screen to //tell you// how it is being done). | + | In a **desktop application**, all activity taking place is within the memory of the computer on which you are working - and computer memory is //extremely// fast. The biggest impacts on speed which you will encounter in this environment is data access to a hard-disk, which is still largely a mechanical device and therefore is extremely slow by comparison; and, redrawing the screen when a long process is being undertaken. In this latter case the speed delay is not because the display is slow, but because operating systems typically regard screen updates to be the least important of all of the actions being undertaken (i.e. the //process// of adding 2+2 is regarded as more important than updating the screen to //tell you// how it is being done). Screen updates therefore take place all at once, when all of the work is done. |
| In an **online application**, activity takes place in a mixture of your local Internet Browser (which may be MS Edge, Opera, Chrome, Safari, Brave etc.), and the server on which the application is running. Local activities will remain extremely fast, such as the operation of common on-screen controls like text boxes, buttons, sliders etc. Activities taking place on the server are also extremely fast, as the server is usually an even bigger, faster and more powerful machine than the one that you are working on. | In an **online application**, activity takes place in a mixture of your local Internet Browser (which may be MS Edge, Opera, Chrome, Safari, Brave etc.), and the server on which the application is running. Local activities will remain extremely fast, such as the operation of common on-screen controls like text boxes, buttons, sliders etc. Activities taking place on the server are also extremely fast, as the server is usually an even bigger, faster and more powerful machine than the one that you are working on. | ||
| Line 31: | Line 31: | ||
| All of the following can slow down the communication between your browser and the server: | All of the following can slow down the communication between your browser and the server: | ||
| + | |||
| + | * **Browsers 'cache' data and images that have been downloaded from the internet**, in an attempt to increase responsiveness of future downloads. Sometimes you browser will seem to stop for a second or two, then burst into life again - this is not an internet delay as such, but your local browser saving the data into a local 'cache'. | ||
| * Other **large applications running simultaneously** - this can cause issues if the applications are consuming a great deal of memory, and therefore forcing your browser to cache more often. | * Other **large applications running simultaneously** - this can cause issues if the applications are consuming a great deal of memory, and therefore forcing your browser to cache more often. | ||
| Line 45: | Line 47: | ||
| * **Very high usage of the application** at a particular moment in time - Esferico have introduced load-balanced servers to counter this eventuality. | * **Very high usage of the application** at a particular moment in time - Esferico have introduced load-balanced servers to counter this eventuality. | ||
| + | |||
| + | * Sometimes, **your local workstation may connect to the internet using a 'proxy'** which 'caches' data in a similar way to your browser. A proxy is often a local server on your local internet. Unfortunately, //sometimes// proxies are geared towards static web-pages rather than dynamic cloud applications and find it hard to make a distinction between stored images and dynamic data that needs to be refreshed anew each time requested. This can introduce a finite amount of time to the recovery of data. | ||
| While this collection of known communications bottle necks seem extreme, the reality is that the delay is actually very minor - potentially fractions of a second, with some of the above limited to slowing the initial connection and not the overall speed of the communication itself (what in networking is called //latency//). | While this collection of known communications bottle necks seem extreme, the reality is that the delay is actually very minor - potentially fractions of a second, with some of the above limited to slowing the initial connection and not the overall speed of the communication itself (what in networking is called //latency//). | ||
| Line 53: | Line 57: | ||
| ==== Thing to do / not do when using a Cloud Application ==== | ==== Thing to do / not do when using a Cloud Application ==== | ||
| - | In a practical sense, communications speed between the browser and the server actually impact only one thing - //user perception//. While computers are very fast at performing certain tasks compared to humans, even //extremely small differences// in time are often exaggerated by humans to seem like major delays. | + | In a practical sense, communications speed between the browser and the server actually impact only one thing - **//user perception//**. |
| + | |||
| + | While computers are very fast at performing certain tasks compared to humans, even //extremely small differences// in time are often exaggerated by human brains to seem like major delays. | ||
| Gradually, users adjust to how internet based applications work but here are some things to consider: | Gradually, users adjust to how internet based applications work but here are some things to consider: | ||
| Line 70: | Line 76: | ||
| * Some long processes or data downloads display a 'waiting' or 'percentage bar' to tell you that an activity is still underway. **Wait for the bar to finish** before clicking functions, or if the process gives your ability to do so, **click a 'stop' or 'abort' button** prior to selecting another function. | * Some long processes or data downloads display a 'waiting' or 'percentage bar' to tell you that an activity is still underway. **Wait for the bar to finish** before clicking functions, or if the process gives your ability to do so, **click a 'stop' or 'abort' button** prior to selecting another function. | ||
| - | * | + | |
| ---- | ---- | ||
pergamonmystic/linkedhelp/patience.1632913208.txt.gz · Last modified: 2021/09/29 11:00 by admin
Page Tools
