Fundamental knowledge-EngineerPro
Fundamental knowledge-EngineerPro
1
EngineerPro- Fanpage:https://www.facebook.com/EngineerPro.Official
Tổng hợp các câu hỏi về CS
fundamental
= or != operators (but are very fast). They are not used for
possible.
- B-Tree Index:
+ B-tree stands for “balanced tree”, it’s a self-balancing tree
data structure that maintains sorted data and allows
searches.
+ A B-tree index can be used for column comparisons in
expressions that use the =, >, >=, <, <=, or BETWEEN
operators. The index also can be used for LIKE
comparisons if the argument to LIKE is a constant string
that does not start with a wildcard character
HTTP methods tell the server what to do. There are a lot of HTTP
methods but we’ll study the most common ones: GET, POST, HEAD,
PUT, or DELETE.
UDP only adds the absolute bare minimum functionality over the
network layer. So it…
11. What is eventual consistency? (Em có thể đọc thêm link này)
https://stackoverflow.com/questions/21595048/how-python-dict-stores
-key-value-when-collision-occurs
19. Compare thread vs process
https://www.geeksforgeeks.org/difference-between-process-and-threa
d/
Answer: https://en.wikipedia.org/wiki/Process_state
https://en.wikipedia.org/wiki/Virtual_memory
Answer: https://www.geeksforgeeks.org/swap-space-in-operating-system/
It is sometimes said that the operating system takes one of two approaches when
solving most any space-management problem. The first approach is to chop
things up into variable-sized pieces, as we saw with segmentation in virtual
memory. Unfortunately, this solution has inherent difficulties. In particular,
when dividing a space into different-size chunks, the space itself can become
fragmented, and thus allocation becomes more challenging over time.
Thus, it may be worth considering the second approach: to chop up space into
fixed-sized pieces. In virtual memory, we call this idea paging, and it goes back to
an early and important system, the Atlas. Instead of splitting up a process’s
address space into some number of variable-sized logical segments (e.g., code,
heap, stack), we divide it into fixed-sized units, each of which we call a page.
Correspondingly, we view physical memory as an array of fixed-sized slots called
page frames; each of these frames can contain a single virtual-memory page
24. What is the segmentation technique in virtual memory?
So far we have been putting the entire address space of each process in memory.
With the base and bounds registers, the OS can easily relocate processes to
different parts of physical memory. However, you might have noticed something
interesting about these address spaces of ours: there is a big chunk of “free” space
right in the middle, between the stack and the heap.
As you can imagine from the figure below, although the space between the stack
and heap is not being used by the process, it is still taking up physical memory
when we relocate the entire address space somewhere in physical memory; thus,
the simple approach of using a base and bounds register pair to virtualize
memory is wasteful.
It also makes it quite hard to run a program when the entire address space
doesn’t fit into memory; thus, base and bounds are not as flexible as we would like.
Answer: https://en.wikipedia.org/wiki/Inter-process_communication