| /external/skia/include/core/ |
| SkUserConfig.h | 62 /* Skia has certain debug-only code that is extremely intensive even for debug
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| pausing.jd | 112 However, you should avoid performing CPU-intensive work during {@link
|
| stopping.jd | 84 to perform larger, more CPU intensive shut-down operations, such as writing information to a
|
| /developers/build/prebuilts/gradle/AlwaysOn/Wearable/src/main/java/com/example/android/wearable/wear/alwayson/ |
| MainActivity.java | 44 * Why don't we use just one? Handlers are generally less battery intensive and can be triggered
|
| /developers/samples/android/wearable/wear/AlwaysOn/Wearable/src/main/java/com/example/android/wearable/wear/alwayson/ |
| MainActivity.java | 44 * Why don't we use just one? Handlers are generally less battery intensive and can be triggered
|
| /development/samples/ApiDemos/src/com/example/android/apis/app/ |
| ServiceStartArguments.java | 116 // background priority so CPU-intensive work will not disrupt our UI.
|
| /development/samples/MySampleRss/src/com/example/codelab/rssexample/ |
| RssService.java | 84 // we will be making resource-intensive HTTP calls.
|
| /development/samples/browseable/AlwaysOn/src/com.example.android.wearable.wear.alwayson/ |
| MainActivity.java | 44 * Why don't we use just one? Handlers are generally less battery intensive and can be triggered
|
| /external/antlr/antlr-3.4/runtime/Python/ |
| pylintrc | 280 # memory / CPU intensive, so you should disable it if you experiments some
|
| /external/autotest/client/site_tests/graphics_GLBench/ |
| graphics_GLBench.py | 16 """Run glbench, a benchmark that times graphics intensive activities."""
|
| /external/chromium-trace/catapult/third_party/gsutil/third_party/boto/ |
| pylintrc | 260 # memory / CPU intensive, so you should disable it if you experiments some
|
| /external/chromium-trace/catapult/third_party/vinn/third_party/parse5/test/data/simple_api_parsing/nodejsorg/ |
| expected.html | 37 lightweight and efficient, perfect for data-intensive real-time
|
| src.html | 37 lightweight and efficient, perfect for data-intensive real-time
|
| /external/sonic/doc/ |
| index.md | 65 Sonic does all of it's CPU intensive work with integer math, and works well on
|
| /frameworks/base/docs/html/training/articles/ |
| perf-anr.jd | 162 operations or calculations in a broadcast receiver. But instead of doing intensive
|
| /frameworks/base/tools/layoutlib/bridge/tests/src/com/android/layoutlib/bridge/intensive/setup/ |
| ConfigGenerator.java | 17 package com.android.layoutlib.bridge.intensive.setup;
|
| /external/valgrind/memcheck/tests/ |
| vcpu_fbench.c | 43 point (including trig function) intensive real-world
61 application which is math function intensive.
|
| /external/valgrind/perf/ |
| fbench.c | 39 point (including trig function) intensive real-world
57 application which is math function intensive.
|
| /frameworks/native/opengl/tests/hwc/ |
| hwcStress.cpp | 29 * intensive operations are performed just once at the beginning of a group
32 * by moving computationally intensive operations to the beginning of a group.
|
| /docs/source.android.com/src/devices/tech/debug/ |
| asan.jd | 138 environment. The latter can be very CPU-intensive, depending on
|
| /external/chromium-trace/catapult/third_party/coverage/ |
| TODO.txt | 282 - More intensive thread testing.
|
| pylintrc | 323 # memory / CPU intensive, so you should disable it if you experiments some
|
| /external/libchrome/base/message_loop/ |
| message_pump_glib.cc | 56 // doing intensive work, for example the flash plugin. They usually use the
|
| /frameworks/base/docs/html/guide/components/ |
| services.jd | 95 that, if your service is going to do any CPU intensive work or blocking operations (such as MP3
119 default, so you should still create a new thread within the service if it performs intensive or
266 performs intensive or blocking operations while the user interacts with an activity from the same
422 // background priority so CPU-intensive work will not disrupt our UI.
[all...] |
| /frameworks/base/docs/html/guide/topics/resources/ |
| runtime-changes.jd | 72 connection, or perform other intensive operations, then a full restart due to a configuration change
|
