148 karma · joined July 3, 2011
Jestem z Polski == I am from Poland
Jesteś z Polski == You are from Poland
Jestem Polakiem == I am Polish
Jesteś Polakiem == You are Polish
Both have very close meaning but 3&4 seem to be equivalent of examples in other languages given above.Source: I am Polish
Start from trusted resource like: https://www.nhs.uk/conditions/stress-anxiety-depression/low-...
It is possible that you will need to work with therapist who has spent decades debugging and solving problems like yours. If you can't afford therapy try to talk to real people with years of life experience outside of hacker forum.
At the end of the day you will need to understand what is the cause of your problem. Start thinking about it right away.
EDIT: good article how some people are able to function with autism (which may look like treatment but it is not) http://www.nytimes.com/2014/08/03/magazine/the-kids-who-beat...
Supported technologies: https://ruxit.com/ruxit/supportedtechnologies.html
We have pretty cool technology to correlate events into bigger buckets (problems).It is based on tracking of each individual transaction flow through the stack plus discovery of infrastructure topology and performance.
[Edit:spelling ]
1.Table selection - there is predefined set of joined tables we call views. Views have descriptive names e.g. 'Temperature measurements', no underlying tables are shown.
2.Column selection - user selects columns from views using descriptive names , not actual column names . UI clearly indicates columns that land in 'group by' section by calling them dimensions. There is predefined aggregation strategy for all columns that are not dimensions - e.g. average for temperatures or sum for number of measurements. In some cases more that one aggregate is available e.g. average or maximum temperature. User just selects maximum or average temperature not aggregation operator.
3. Filters: user can select simple filters on columns: =<> and string matching for text. All filters are ANDed
4.Sorting: user can select columns to sort on.
5.Display: results are displayed as tables or charts. More that one section may be placed on single report.
The real system has tons of additional features but basic design as design as described above has worked great for years.
> Issues: Super small market?
This is definitely not a small market and there is plenty of competition:
https://news.ycombinator.com/item?id=7340001
http://blog.dataloop.io/2014/01/30/what-we-learnt-talking-to...
Probably hypervisor does not assign CPU every time it is requested but it still manages to assign as much as needed because in the end there is some idle time left.
AWS noisy neighbors problem is very often misunderstood. CPU steal time under linux does NOT mean that somebody is stealing your CPU. It simply means that you wanted to use CPU and hypervisor has given it to another instance. This may happen because you have exceeded your quota or scheduling algorithm selected another pending instance at this very moment and it would give CPU back to you a bit later. In the end in both cases your instance gets fair share.
Great detailed explanations of steal time: https://support.cloud.engineyard.com/entries/22806937-Explan... and: http://www.stackdriver.com/understanding-cpu-steal-experimen.... The latter article is mentioned by OP but seems to be not fully read/understood.
Why does killing and restarting instance help? It likely moves instance to different hardware node with less active neighbors. When your neighbor is not active your instance can use CPU idle cycles of your neighbor! You sort of become the noisy one. Still hypervisor would prevent it once neighbor starts to fully utilize his CPU quota and you are back to square one.
Amazon does not oversubscribe CPU according to their CTO: http://itknowledgeexchange.techtarget.com/cloud-computing/am...
Amazon specifically states that t1.micro instances do not guarantee CPU performance: "Micro instances are a very low-cost instance option, providing a small amount of CPU resources. Micro instances may opportunistically increase CPU capacity in short bursts when additional cycles are available. They are well suited for lower throughput applications and websites that require additional compute cycles periodically, but are not appropriate for applications that require sustained CPU performance."
While CPU sharing is pretty well documented noisy neighbor problem still exists for network and disk resources being shared by multiple instances on the same hardware node. The only way to detect these problems is to track network throughput/loss rate for network and IO stats for disk.
You are guaranteed to avoid noisy neighbors CPU problem by using AWS dedicated instances: http://aws.amazon.com/dedicated-instances/
I work for APM ( Application Performance Management) vendor , I have no business praising AWS.
[Edit:spelling and clarity]
[Edit2: changed CPU scheduling description]
Very fast domain availability check and gives you suggestions for names based on partial input.
Maybe develop great evernote app to solve single but tough problem first?
API is useful for companies like mobile operators or utility providers who have thousands of subscribers who do not pay.
1.6M payment orders, 21 months, 200 staff = ~17 cases per day per person (no holidays and vacations). Sounds doable given it is likely to be batches of claims as described above.