Efficient Go Index
A
- Alexandrescu, Andrei
- Allen, Arnold O., on performance, Behind Performnce
- Allocator (see Go Allocator)
- Andreessen, Marc, on democratization of software, Software gets slower more rapidly than hardware becomes faster
- machine code and, Assembly
B
- (see also efficiency assessment)
- Bentley, Jon Louis
- (see also profiling)
- Branczyk, Frederic
C
- Carruth, Chandler
- Cheney, Dave
- compilation (see Go compiler)
- compiler optimizations, microbenchmarks versus, Compiler Optimizations Versus Benchmark-Compiler Optimizations Versus Benchmark
- complexity analysis, Complexity Analysis-It tells us where the bottleneck is and what part of the algorithm is critical
- practical applications, Practical Applications-It tells us where the bottleneck is and what part of the algorithm is critical
- advantages, When to Use Concurrency
- disadvantages, When to Use Concurrency
- Cox, Russ
- modern computer architecture and, CPU in a Modern Computer Architecture-CPU in a Modern Computer Architecture
D
- documentation, as first citizen, Code Documentation as a First Citizen-Code Documentation as a First Citizen
E
- (see also misconceptions about efficiency)
- formalizing of requirements, Efficiency Requirements Should Be Formalized-Efficiency Requirements Should Be Formalized
- key to pragmatic code performance, The Key to Pragmatic Code Performnce-The Key to Pragmatic Code Performnce
- optimization and (see optimization)
- reacting to efficiency problems, Got an Efficiency Problem? Keep Calm!-Got an Efficiency Problem? Keep Calm!
- complexity analysis, Complexity Analysis-It tells us where the bottleneck is and what part of the algorithm is critical
- functionality phase, Functionality Phase-3. If the tests fail, we have to fix, implement, or design the missing parts
F
- Flake, Halvar, on GC, Garbage Collection
- FR (functional requirements) stage, Efficiency Requirements Should Be Formalized-Efficiency Requirements Should Be Formalized
- functional requirements (FR) stage, Efficiency Requirements Should Be Formalized-Efficiency Requirements Should Be Formalized
- functionality phase of TFBO, Functionality Phase-3. If the tests fail, we have to fix, implement, or design the missing parts
G
- code documentation as first citizen, Code Documentation as a First Citizen-Code Documentation as a First Citizen
- code documentation as first citizen, Code Documentation as a First Citizen-Code Documentation as a First Citizen
- machine code and, Assembly
- formalizing of efficiency requirements, Efficiency Requirements Should Be Formalized-Efficiency Requirements Should Be Formalized
- Gregg, Brendan, on Flame Graph, Flame Graph
- Griesemer, Robert
- Go origins, Designed to Improve Serious Codebases, Simplicity, Safety, and Readability Are Paramount
H
- misconceptions about increasing speed and decreasing cost, Hardware Is Getting Faster and Cheaper-Faster execution is more energy efficient
- stack versus, Go Memory Management
- Hungarian Notation, Readability now versus past
I
- function, Understanding Go Compiler
- manual, Understanding Go Compiler
- forms of, Observability
J
K
- Kennedy, William
- on mechanical sympathy, Understanding Go Compiler
- Kernighan, Brian W.
- Knuth, Donald
- on premature optimization, Readability now versus past
L
- optimizing using concurrency, Optimizing Latency Using Concurrency-A Streamed, Sharded Worker Approach
- worker approach with distribution, A Worker Approach with Distribution-A Worker Approach with Distribution
- worker approach without coordination, A Worker Approach Without Coordination (Sharding)-A Worker Approach Without Coordination (Sharding)
- leak (see resource leaks)
M
- about, Macrobenchmarks
- Bill Kennedy on, Understanding Go Compiler
- microbenchmarks versus, Microbenchmarks Versus Memory Management-Microbenchmarks Versus Memory Management
- values, pointers, and memory blocks, Values, Pointers, and Memory Blocks-Values, Pointers, and Memory Blocks
- documentation of, Latency
- compiler optimizations versus, Compiler Optimizations Versus Benchmark-Compiler Optimizations Versus Benchmark
- memory management versus, Microbenchmarks Versus Memory Management-Microbenchmarks Versus Memory Management
- hardware speed/cost, Hardware Is Getting Faster and Cheaper-Faster execution is more energy efficient
- horizontal scaling versus vertical scaling, We Can Scale Horizontally Instead-We Can Scale Horizontally Instead
N
O
- monitoring versus, Observability
- formalizing of efficiency requirements, Efficiency Requirements Should Be Formalized-Efficiency Requirements Should Be Formalized
- stakeholders and, Understand Your Goals
- optimizing latency using concurrency, Optimizing Latency Using Concurrency-A Streamed, Sharded Worker Approach
P
R
- code after optimization as more readable, Code after optimization can be more readable-Code after optimization can be more readable
- now versus past, Readability now versus past
S
- misconceptions about efficiency, We Can Scale Horizontally Instead-We Can Scale Horizontally Instead
- vertical, We Can Scale Horizontally Instead
- worker approach without coordination, A Worker Approach Without Coordination (Sharding)-A Worker Approach Without Coordination (Sharding)
- Sutter, H.
T
- TFBO (test, fix, benchmark, optimize) development flow, Efficiency-Aware Development Flow-9. Release and enjoy!
- time to market (financial impact), Time to Market Is More Important-Time to Market Is More Important
U
V
- vertical scalability, We Can Scale Horizontally Instead
W
Fair Use Sources
SHORTEN THIS to 20 ITEMS! navbar_golang
Golang: Golang Fundamentals, Golang Inventor - Golang Language Designer: Ken Thompson, Robert Griesemer, Rob Pike of Google, Go abstraction, Go agile, Go ahead-of-time (AOT), Go AI, Go algebraic data types, Go algorithms, Go Android, Go anonymous functions, Go AOP, Go AOT, Go APIs, Go arguments, Go ARM, Go arithmetic, Go arrays, Go aspect-oriented, Go assignment, Go associative arrays, Go async, Go asynchronous callbacks, Go asynchronous programming, Go automatic variables, Go automation, Go Avro, Go backend, Go backwards compatibility, Go block scoped, Go Booleans, Go Boolean expressions, Go buffer overflow, Go builds, Go built-in types, Go bytecode, Go cache, Go caching, Go call by reference, Go call by value, Go callbacks, Go call stack, Go casting, Go characters, Go Chocolatey, Go CI/CD, Go classes, Go CLI, Go client-side, Go closures, Go cloud (Go Cloud Native-Go AWS-Go Azure-Go GCP-Go IBM Cloud-Go IBM Mainframe-Go OCI), Go code smells, Go coercion, Go collections, Go command-line interface, Go commands, Go comments, Go compilers, Go complex numbers, Go composition, Go configuration, Go concurrency, Go concurrent programming, Go conditional expressions, Go conferences, Go constants, Go constructors, Go containers, Go control flow, Go control structures, Go coroutines, Go crashes, Go creators, Go currying, Go databases, Go data manipulation, Go data persistence, Go data science, Go data serialization, Go Built-In Data Types, Go data structures, Go data synchronization, Go dates, Go dates and times, Go deadlocks, Go debugging, Go declarative, Go deferred callbacks, Go delegates, Go delegation, Go dependency injection, Go design patterns, Go designers, Go destructors, Go DevOps, Go dictionaries, Go dictionary comprehensions, Go DI, Go distributed software, Go distributions, Go distros, Go DL, Go Docker, Go do-while, Go DSL, Go duck typing, Go dynamic binding, Go dynamic scope, Go dynamically scoped, Go dynamically typed, Go dynamic variables, Go eager evaluation, Go embedded, Go encapsulation, Go encryption, Go enumerated types, Go enumeration, Go enums, Go environment variables, Go errors, Go error handling, Go evaluation strategy, Go event-driven, Go event handlers, Go event loops, Go exception handling, Go executables, Go execution, Go expressions, Go FaaS, Go Facebook, Go fibers, Go fields, Go file input/output, Go file synchronization, Go file I/O, Go filter, Go first-class functions, Go fold, Go foreach loops, Go fork-join, Go floating-point, Go FP, Go frameworks, Go FreeBSD, Go frontend, Go functions, Go functional, Go functional programming, Go function overloading, Go garbage collection, Go generators, Go generator expressions, Go generics, Go generic programming, Go GitHub, Go global variables, Go GraphQL, Go gRPC, Go GUI, Go hashing, Go heap, Go heap allocation, Go hello world, Go higher-order functions, Go history, Go Homebrew, Go HTTP, Go idempotence, Go IDEs, Go import, Go imperative, Go immutable values, Go immutability, Go inheritance, Go influenced, Go influenced by, Go installation, Go integers, Go integration testing, Go interfaces, Go internationalization, Go interpreters, Go interprocess communication (IPC), Go iOS, Go IoT, Go IPCs, Go ISO Standard, Go iteration, Go JetBrains, Go JIT, Go JSON, Go JSON-RPC, Go JSON Web Tokens, Go JSON Web Token (JWT), Go Just-in-time (JIT), Go JWT, Go K8S, Go keywords, Go lambdas, Go language spec, Go lazy evaluation, Go lexically scoped, Go lexical scoping, Go libraries, Go linters, Go Linux, Go lists, Go list comprehensions, Go literals, Go localization, Go local variables, Go locks, Go logging, Go logo, Go looping, Go macOS, Go map, Go mascot, Go math, Go member variables, Go memoization, Go memory addressing, Go memory allocation, Go malloc, Go memory management, Go memory safety, Go message queues, Go metaclasses, Go meta-programming, Go methods, Go method overloading, Go MFA, Go ML, Go microservices, Go Microsoft, Go mobile dev, Go modules, Go modulo operators, Go monitoring, Go multiprocessing, Go multi-threaded, Go mutable values, Go mutability, Go mutex (Go mutual exclusion), Go namespaces, Go natural language processing (NLP), Go networking, Go network programming, Go NLP, Go non-blocking, Go non-blocking I/O, Go null, Go null reference, Go null coalescing operators, Go numbers, Go number precision, Go OAuth, Go objects, Go object code, Go object comparisons, Go object creation, Go object creators, Go object destruction, Go object destructors, Go object lifetime, Go object-oriented constructors, Go object-oriented programming, Go object serialization, Go observability, Go OOP, Go operators, Go operator overloading, Go optimizations, Go organizations, Go ORMs, Go packages, Go package managers, Go pass by reference, Go pass by value, Go parallel computing, Go parallel programming, Go parallelism, Go parameters, Go people, Go performance, Go persistence, Go pipelines, Go pointers, Go polymorphism, Go primitives, Go primitive data types, Go probability, Go procedural, Go processes, Go producer-consumer, Go programmers, Go programming, Go programming paradigm, Go program structure, Go program termination, Go Protocol Buffers (Protobuf), Go Protocol Buffers, Go Protobuf, Go proxies, Go public-key encryption, Go PKI, Go pure functions, Go race conditions, Go random, Go reactive, Go readability, Go records, Go recursion, Go reentrancy, Go refactoring, Go reference counting, Go reference types, Go referential transparency, Go reflection, Go regex, Go remote procedure calls (RPC), Go REPL, Go reserved words, Go REST, Go REST APIs, Go RHEL, Go RPCs, Go runtimes, Go safe navigation operators, Go SDK, Go secrets, Go security, Go serialization, Go serverless, Go server-side, Go sets, Go set comprehensions, Go side effects, Go signed integers, Go SMTP, Go Snapcraft, Go social media, Go sockets, Go source code, Go source-to-source compiler, Go SQL, Go SSL - Go SSL-TLS, Go Single sign-on (SSO), Go SSO, Go StackOverflow, Go stack, Go stack allocation, Go Stack overflow, Go standards, Go standard errors, Go standard input, Go standard library, Go standard operators, Go standard output, Go state, Go statements, Go strings, Go string concatenation, Go string functions, Go string operations, Go scheduling, Go scientific notation, Go scope, Go scope rules, Go scoping, Go scripting, Go static analyzers, Go statically scoped, Go static scoping, Go statically typed, Go static variables, Go statistics, Go strongly typed, Go structural typing, Go synchronization, Go syntax, Go systems programming, Go TCP/IP, Go TDD, Go testing, Go test frameworks, Go threads, Go thread-local storage (TLS), Go TLS, Go thread locking, Go thread locks, Go thread safety, Go thread scheduling, Go thread synchronization, Go times, Go timers, Go to JavaScript, Go tools, Go toolchain, Go transpiler, Go transpiling to JavaScript, Go truth values, Go tuples, Go type checking, Go type conversion, Go type inference, Go type safety, Go type system, Go web dev, Go while loops, Go work stealing, Go values, Go value types, Go variables, Go variable lifetime, Go variable scope, Go versions, Go virtual environments, Go virtual machine, Go Ubuntu, Go Unicode, Go unit testing, Go unsigned integers, Go usability, Go weakly typed, Go Windows, Go wrappers, Go written using, Go x86-64-Go AMD64, Go XML, Go YAML, Go Awesome list;
Go topics-Go courses-Go books-Go docs. (navbar_golang and navbar_golang_detailed)
navbar_programming and navbar_programming_detailed
© 1994 - 2024 Cloud Monk Losang Jinpa or Fair Use. Disclaimers
SYI LU SENG E MU CHYWE YE. NAN. WEI LA YE. WEI LA YE. SA WA HE.