In database systems, indexes are used to make queries faster by helping the system find data quickly, similar to how a book index helps you find pages faster. However, the author says an index can still be “slow” when the database needs to do extra work after using the index. For example, if the query matches many rows or if the data is stored in different parts of memory, the database must open and read each row separately, which takes time. This idea connects to what I’ve learned in computer science and my experience with systems like SAP and MES, where performance depends not only on structure but also on how data is accessed. So, a “slow index” means the index works, but the process of fetching all the related data makes the query slower overall.
This week, I learned more about probability distributions, density plots, histograms, and how to visualize data using Python libraries such as Pandas, Matplotlib, Seaborn, and SciPy. I practiced creating density plots, box plots, cumulative density plots, and histograms using real datasets. I also learned how changing things like bin width, bandwidth, transparency, and sample size can affect the appearance and interpretation of graphs. Another important topic was understanding skewness and how transformations such as log10 can help make heavily skewed data easier to analyze. One thing I found interesting was how probability density functions (PDFs) and histograms can represent the same data differently. Before this week, I thought graphs mostly showed the same information in different styles, but now I understand that each type of plot has a different purpose and can make patterns easier or harder to notice. I also learned that larger sample sizes tend to reflect the true distribution...
Comments
Post a Comment